T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned npm CLI Execution Through npx
- Content
View full analysis
- Remediation
View remediation
install drop-spindle-spinning-basics ``` Do not use version ranges or floating tags such as `latest`. 2. Configure and document an explicitly trusted npm registry rather than relying on ambient registry configuration. 3. Verify package provenance and integrity before execution. Record the expected package digest and compare it against the downloaded artifact. 4. Review the pinned package, its CLI entry point, lifecycle scripts, and transitive dependency lockfile before recommending execution. 5. Prefer a platform-managed installer that retrieves a verified artifact separately from execution and rejects artifacts whose signatures or hashes do not match approved values. 6. Run installation with the minimum required privileges in an isolated environment. Do not invoke the command as an administrator or root user. 7. Keep the version and integrity metadata in the reviewed skill manifest so future dependency updates require an explicit security review. ]]>
