Caveat verdict

figma

openclaw-figma

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Figma design asset integration using FIGMA_TOKEN for the official Figma API and MCP server; all operations are standard design-to-code workflows with explicitly declared external contacts.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

45
security
70
transparency
70
maintenance

Findings (4)

Pattern match critical

Possible hardcoded credential

references/guide-for-agents.md · code · TOKEN="$FIGMA_TOKEN

Pattern match high

Accesses OpenClaw config/secrets directly

references/guide-for-agents.md · code · ~/.openclaw/.env

Pattern match low

Python urllib.request — network access

scripts/figma_api.py · prose · downgraded · urllib.request

Pattern match low

Python os.environ.get — reads environment variable

scripts/figma_api.py · prose · downgraded · os.environ.get(

Permissions & capabilities

No declared permissions — minimal attack surface.

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API