T08 · Insecure Dependencies
- Location
SKILL.md:116- Finding
Unpinned Third-Party Package Execution Through npx
- Content
View full analysis
- Remediation
View remediation
`, rather than resolving the latest release. - Verify the package's publisher, repository, provenance attestations, and npm integrity metadata before use. - Maintain a lockfile when integrating the package into a project and review dependency changes before updating it. - Prefer installing dependencies during a controlled build phase rather than downloading and executing them dynamically at runtime. - Disable package lifecycle scripts where compatible with the package's operation. - Run the MCP server inside a restricted container or sandbox with: - A non-privileged user. - A minimal environment-variable allowlist. - Read-only or narrowly scoped filesystem access. - Restricted outbound network access. - No access to unrelated credentials or wallet secrets. - Include the package source or a reviewed commit reference in the audited project when practical. ]]>
