T08 · Insecure Dependencies
- Location
SKILL.md:28- Finding
Unpinned npm Package Execution Through npx
- Content
View full analysis
- Remediation
View remediation
``` 2. Prefer installing the package in a dedicated project with an exact version and a committed lockfile, then invoke the lockfile-resolved local executable. 3. Verify the package's registry provenance and integrity metadata before execution. Where supported, enforce approved package hashes or signatures in deployment tooling. 4. Disable automatic upgrades. Review new releases and their dependency changes before updating the pinned version. 5. Run the MCP client with least privilege in an isolated account, container, or sandbox. Restrict filesystem and network access to what the integration requires. 6. Provide the API key only to the isolated MCP process. Do not expose unrelated credentials through inherited environment variables, and rotate the key if package compromise is suspected. 7. Document the exact reviewed package version and required permissions so users can make an informed trust decision. ]]>
