Caveat verdict

use-developer-controlled-wallets

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

Circle developer-controlled wallet SDK integration; uses env vars for credentials (CIRCLE_API_KEY, ENTITY_SECRET), routes only to Circle API, and all behavior matches the stated wallet management purpose.

⚠ 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.

60
security
40
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (2)

Confirmed in code medium

Accesses process.env — reads environment variables

SKILL.md · code

Pattern match medium

Accesses sensitive environment variables

SKILL.md · code · process.env.CIRCLE_API_KEY

Permissions & capabilities

No declared permissions — minimal attack surface.

package_installcredential_access

Is this flag fair?

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