T08 · Insecure Dependencies
- Location
SKILL.md:25- Finding
Unpinned Global npm Package Installation
- Content
View full analysis
- Remediation
View remediation
``` 2. Prefer a project-local installation over a global installation to reduce the affected scope. 3. Maintain a lockfile and use `npm ci` so dependency resolution is reproducible. 4. Verify package provenance and integrity through trusted registry metadata, integrity hashes, signatures, or npm provenance attestations. 5. Avoid the ad hoc `npm install pkce-challenge --no-save` mutation. Use a reviewed release in which the dependency is correctly declared and locked. 6. Disable package lifecycle scripts during installation where operationally possible, then explicitly review any scripts that are required. 7. Run the CLI under a dedicated, least-privileged account without access to unrelated credentials or sensitive files. 8. Document the exact supported package version and establish a controlled process for reviewing and updating it. ]]>
