T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Global npm Dependency with Access to Authentication Credentials
- Content
View full analysis
- Remediation
View remediation
``` 2. Prefer a project-local installation with a committed lockfile over a global installation. 3. Use `npm ci` with a reviewed `package-lock.json` so dependency resolution is reproducible. 4. Verify package provenance, publisher identity, and registry source before installation. 5. Where supported, verify package signatures or integrity hashes and disable unnecessary lifecycle scripts. 6. Periodically review and deliberately update the pinned package and its transitive dependencies after security testing. 7. Run the client with the least-privileged account necessary and restrict its filesystem access to reduce the effect of a supply-chain compromise. ]]>
