remotion-best-practices

Fail

Audited by Snyk on Aug 2, 2026

Risk Level: HIGH
Full Analysis

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (low risk: 0.10). The required workflow “Looking up Remotion APIs and documentation” uses Algolia search and then fetches Remotion documentation pages as Markdown chosen from search results, so outsider-authored free text from search results/pages can be ingested at runtime via fetched .md content.

MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).


HIGH W008: Secret detected in skill content (API keys, tokens, passwords).

  • Secret detected (high risk: 1.00). I flagged the Algolia API key because a literal, high-entropy token appears inline in the example POST URL: "3e42dbd4f895fe93ff5cf40d860c4a85" — it is a long, random-looking string and therefore meets the definition of a secret (an API key) present in the documentation.

Ignored items / not flagged:

  • Environment variable names such as REMOTION_MAPTILER_KEY, REMOTION_GOOGLE_MAPS_API_KEY, REMOTION_MAPBOX_TOKEN, and other references to GOOGLE_KEY are only variable names (placeholders) and do not contain literal credential values.
  • Guidance URLs, example commands, and simple example strings (e.g., "your-service-role-key" style placeholders) are documentation placeholders and intentionally ignored.

Issues (3)

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

W012
MEDIUM

Unverifiable external dependency detected (runtime URL that controls agent).

W008
HIGH

Secret detected in skill content (API keys, tokens, passwords).

Audit Metadata
Risk Level
HIGH
Analyzed
Aug 2, 2026, 11:57 PM
Issues
3
Security Audit — snyk — remotion-best-practices