T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unpinned Global Installation of a Third-Party npm Package
- Content
View full analysis
- Remediation
View remediation
``` 2. Specify and validate the trusted npm registry rather than relying on an arbitrary user-configured registry. 3. Publish and verify expected package integrity information or provenance where the installation workflow supports it. 4. Prefer a project-local installation over a global installation to reduce system-wide exposure. 5. Use a lockfile or another reproducible dependency mechanism when integrating the CLI into an automated project workflow. 6. Disable npm lifecycle scripts during installation when compatible with the package, and explicitly review any scripts that must run. 7. Document package publisher and provenance verification steps before installation or execution. 8. Run the CLI with least privilege and avoid installation through an administrator or root account. ]]>
