T08 · Insecure Dependencies
- Location
skill.md:12- Finding
Unpinned Global Installation of a Third-Party npm Package
- Content
View full analysis
- Remediation
View remediation
``` 2. Verify the package's official npm identity, publisher, source repository, and release provenance before recommending installation. 3. Publish and verify expected package integrity information or signed release provenance where supported. 4. Prefer a project-local installation governed by a committed lockfile instead of a global installation: ```bash npm install --save-exact agent-browser@ ``` 5. Invoke the locally installed binary through a controlled package script or an explicitly resolved path. 6. Review the package and its transitive dependency tree for lifecycle scripts before adoption. Disable installation scripts with `--ignore-scripts` where compatible with the package's operation. 7. Run browser automation under a dedicated, least-privileged account or sandbox without access to unrelated credentials and sensitive files. 8. Establish a dependency update process in which new versions are reviewed and tested before the pinned version is changed. ]]>
