T08 · Insecure Dependencies
- Location
SKILL.md:193- Finding
Unpinned npm Dependencies and Global Package Installation
- Content
View full analysis
- Remediation
View remediation
postcss@ autoprefixer@ ``` 2. Commit and review `package-lock.json`, and use `npm ci` in automated or reproducible environments. 3. Avoid global package installation. Install tools as project-local development dependencies and invoke the locked local binary through package scripts. 4. Configure a trusted npm registry and verify package names, publishers, provenance, and integrity metadata before installation. 5. Audit both direct and transitive dependencies with appropriate software-composition-analysis tooling. 6. Consider disabling lifecycle scripts during initial inspection with `npm ci --ignore-scripts`, then explicitly enable only reviewed scripts where operationally feasible. 7. Run installation and builds in an isolated, least-privileged environment without production credentials. ]]>
