T08 · Insecure Dependencies
- Location
SKILL.md:197- Finding
Unpinned Global Package and Browser Component Installation
- Content
View full analysis
- Remediation
View remediation
``` 2. Prefer a project-local dependency over global installation, and commit a lockfile generated with a trusted npm client. 3. Use `npm ci` with a reviewed lockfile in automated or reproducible environments. 4. Record and verify package provenance and integrity, including the expected npm package digest and publisher identity. 5. Pin Chromium and other downloaded components to reviewed versions and verify cryptographic checksums or signatures before execution. 6. Avoid `--with-deps` by default. If system dependencies are required, list them explicitly and install them through the operating system's trusted package manager. 7. Run installation without administrative privileges whenever possible and isolate browser automation in a restricted container or dedicated low-privilege account. 8. Review npm lifecycle scripts and the transitive dependency tree before approving version updates. ]]>
