T08 · Insecure Dependencies
- Location
SKILL.md:113- Finding
Unpinned Global npm Dependency Creates a Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
``` 2. Prefer a project-local dependency and invoke it through a package script or `npx --no-install` rather than installing it globally. 3. Commit and enforce a lockfile with package integrity values. 4. Document the expected npm registry, package publisher, source repository, and reviewed release checksum. 5. Disable npm lifecycle scripts during installation where feasible, then run only explicitly reviewed setup operations. 6. Avoid elevated installation unless it is strictly necessary. 7. Establish a process to review and test dependency upgrades before changing the pinned version. ]]>
