vibefigma-figma-to-react

Fail

Audited by Snyk on May 17, 2026

Risk Level: HIGH
Full Analysis

HIGH W007: Insecure credential handling detected in skill instructions.

  • Insecure credential handling detected (high risk: 0.90). The prompt includes examples that pass Figma tokens directly (e.g., --token YOUR_TOKEN, figmaToken in API JSON, and inline .env/token placeholders), which encourages embedding secret values verbatim in commands and requests and thus creates an exfiltration risk.

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

  • Third-party content exposure detected (high risk: 0.90). The skill directly fetches and ingests user-generated Figma files via the Figma API / figmaUrl (see CLI/API usage and convertFigmaToReact calls in SKILL.md), and those external designs are parsed and used to generate code and drive file/output actions, so untrusted third-party content can influence agent behavior.

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

  • Potentially malicious external URL detected (high risk: 0.80). The skill instructs users to run the vibefigma CLI via npx (which downloads and executes the package from the npm registry — e.g. https://registry.npmjs.org/vibefigma) at runtime, meaning remote code is fetched and executed and the skill depends on that external package.

Issues (3)

W007
HIGH

Insecure credential handling detected in skill instructions.

W011
MEDIUM

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

W012
MEDIUM

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

Audit Metadata
Risk Level
HIGH
Analyzed
May 17, 2026, 03:24 PM
Issues
3