T08 · Insecure Dependencies
- Location
SKILL.md:351- Finding
Unpinned npm Package Is Automatically Downloaded and Executed with API Key Access
- Content
View full analysis
- Remediation
View remediation
"], "env": { "SIXTYFOUR_API_KEY": "your_key" } } } } ``` 2. Install the pinned dependency through a package manifest and committed lockfile rather than downloading the latest package at every launch. 3. Verify package provenance, publisher identity, release signatures where available, and npm integrity metadata before installation. 4. Remove `-y` where automatic installation is unnecessary so unexpected downloads require explicit approval. 5. Prefer `--no-install` during runtime after performing a separate, controlled installation step. 6. Review the package and its transitive dependencies before updating the pinned version. 7. Use a narrowly scoped API key, impose usage or billing limits where supported, and document immediate key rotation procedures. 8. Run the MCP server in a restricted environment with minimal filesystem, environment-variable, and network access. 9. Update both `SKILL.md` and `README.md` so all installation examples consistently use the pinned and verified dependency workflow. ]]>
