insforge-cli

HIGH W007: Insecure credential handling detected in skill instructions.

• Insecure credential handling detected (high risk: 1.00). The prompt includes examples that place secret values directly into command-line arguments, JSON flags, and project files (e.g., deployments env set VITE_INSFORGE_ANON_KEY ik_xxx, inline --env '{"...":"ik_xxx"}', and .insforge/project.json with api_key), which would require the LLM/agent to emit secrets verbatim and therefore presents a high exfiltration risk.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

• Direct money access detected (high risk: 1.00). The skill explicitly contains payment gateway operations for Stripe: commands to set Stripe test/live secret keys, sync products/prices/customers/subscriptions, configure webhooks, inspect payment history, and create/update/delete Stripe products and prices. Those are specific, first-class payment operations (managing keys and mutating Stripe catalog/customers/subscriptions), not generic HTTP or browser automation. This meets the "Payment Gateways" criterion for Direct Financial Execution.