External Script Fetching
- Category
- Supply Chain
- Confidence
- 90% confidence
- Finding
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
- Content
md he source.** Read the API routes, auth scheme, README and existing OpenAPI before writing. Never invent endpoints. - **Steps run by kind**, as in `register`: `claude:` do it; `approve:` show the command and what becomes public, then wait for a yes; `human:` give the user a checklist (accounts, payment, credentials, DNS, forms, video). - **Installs are pinned and gated.** Any command that installs or downloads code (`npx`, `npm create`, `npm install <pkg>`, `brew install`, `pip install`, `uvx`, `curl | sh`) runs only as an `approve:` step, whatever section of a recipe or row it appears in: show the exact command, wait for a yes, then run it. The package must carry an exact version (`pkg@1.2.3`), never `@latest` or a bare name. If a pin is older than 90 days, or a tool cannot be pinned (Homebrew installs the current formula), look up the current version, show it next to the pinned one, and wait. - **No secrets in files.** Use `<YOUR_API_KEY>` placeholders, and read keys from the environm
