T08 · Insecure Dependencies
- Location
setup.md:23- Finding
Unpinned npm Dependency Installation
- Content
View full analysis
- Remediation
View remediation
``` 2. Include a reviewed `package-lock.json` and use reproducible installation: ```bash npm ci ``` 3. Verify lockfile integrity and review changes to the direct and transitive dependency graph before upgrades. 4. Run dependency installation as an unprivileged user and never recommend `sudo npm install`. 5. Consider disabling lifecycle scripts during initial verification: ```bash npm ci --ignore-scripts ``` If Puppeteer's required installation scripts must subsequently run, review and execute them in a sandboxed environment. 6. Document Puppeteer's browser-download behavior and pin or verify downloaded browser artifacts where feasible. 7. Use automated dependency auditing and controlled update tooling, but do not treat an audit command as a substitute for version pinning and provenance review. ]]>
