T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned npm CLI and Mutable Repository Installation
- Content
View full analysis
- Remediation
View remediation
add ... ``` 2. Pin repository content to a verified commit SHA or immutable signed release rather than using only the mutable owner/repository reference. 3. Publish and verify cryptographic checksums or signatures for the expected Skill package before installation. 4. Avoid global installation unless it is operationally required. Prefer a project-local or otherwise isolated installation to limit persistence and impact. 5. Use a lockfile or controlled internal package registry where the installation workflow supports it. 6. Document the expected package publisher, repository URL, version, commit hash, and verification procedure so users can detect dependency substitution. 7. Run installation in a least-privilege environment without administrative rights, production credentials, or unnecessary filesystem access. 8. Periodically review and update pinned versions through a controlled dependency-update process rather than allowing implicit upgrades during installation. ]]>
