insforge-cli
Fail
Audited by Snyk on May 18, 2026
Risk Level: HIGH
Full Analysis
HIGH W007: Insecure credential handling detected in skill instructions.
- Insecure credential handling detected (high risk: 0.80). The prompt includes multiple examples and commands that pass secret values directly on the command line or embed them verbatim into generated JSON/CLI (e.g.,
secrets add <key> <value>,--env '{"..._ANON_KEY":"ik_xxx"}',deployments env set KEY VALUE, andsecrets get <key>which returns decrypted values), meaning an agent following the skill may need to output secret values verbatim — a high exfiltration risk.
MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).
- Potentially malicious external URL detected (high risk: 0.90). The skill instructs installing flyctl with a runtime command that fetches and executes remote code ("curl -L https://fly.io/install.sh | sh"), and the CLI's source-mode deploy explicitly requires flyctl on PATH, so this external URL is used at runtime to retrieve and run code required for the workflow.
MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).
- Direct money access detected (high risk: 1.00). The skill explicitly includes a "Payments" subsystem built around Stripe: commands to set Stripe test/live secret keys, sync products/prices/customers/subscriptions, configure webhooks, and create/update/delete Stripe products and prices. It directly exposes payment-gateway operations (Stripe) and secret management for Stripe keys, which are specific financial execution capabilities (payment gateway management).
Issues (3)
W007
HIGHInsecure credential handling detected in skill instructions.
W012
MEDIUMUnverifiable external dependency detected (runtime URL that controls agent).
W009
MEDIUMDirect money access capability detected (payment gateways, crypto, banking).
Audit Metadata