T08 · Insecure Dependencies
- Location
INSTALL.md:69- Finding
Unpinned Global Installation of a Third-Party Browser Automation Package
- Content
View full analysis
- Remediation
View remediation
``` 2. Install the package as a project-local dependency instead of globally, and invoke it through `npx --no-install` or a package script. 3. Commit a lockfile containing resolved package versions and integrity values. 4. Verify the official package name, publisher, registry URL, release provenance, and checksums before recommending installation. 5. Review npm lifecycle scripts and consider installation with lifecycle scripts disabled when compatible: ```bash npm ci --ignore-scripts ``` 6. If a separate browser-component installation step is unavoidable, document exactly which hosts, artifacts, hashes, and filesystem locations it uses. 7. Avoid recommending `--with-deps` as a generic troubleshooting step. List required system packages explicitly and require users to review them before privileged installation. 8. Advise users not to run npm or browser installation commands as root or through `sudo`. ]]>
