T08 · Insecure Dependencies
- Location
SKILL.md:134- Finding
Execution of an Unpinned npm Package Through npx
- Content
View full analysis
- Remediation
View remediation
--help ``` 2. Prefer installing the dependency through a committed lockfile from an approved registry, and then prohibit implicit downloads: ```bash npm ci npx --no-install mp-skills --help ``` 3. Record and verify the expected package integrity hash. Use registry allowlisting, package signatures, or provenance verification where supported. 4. Validate that the resolved generator and validator directories are located under the expected verified package installation directory before reading instructions or executing scripts from them. 5. Do not automatically trust paths printed by package output. Reject absolute or unexpected paths outside the approved installation root and resolve symbolic links before validation. 6. Review and pin the transitive dependency graph. Enable automated dependency scanning and require explicit approval before upgrading `mp-skills`. 7. Execute generator and validator scripts in a constrained environment with minimum filesystem access, restricted network access, and no unnecessary credentials. 8. Replace the setup instruction with a version-pinned, integrity-verified installation procedure and document the exact approved package version. ]]>
