T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Third-Party Installation and Execution
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish and verify the expected npm integrity digest or a cryptographically signed release before installation. 3. Pin source installations to a reviewed full commit hash: ```bash git clone https://github.com/vercel-labs/agent-browser cd agent-browser git checkout --detach ``` 4. Require a committed lockfile and use a frozen-lockfile installation mode so dependency resolution cannot silently change: ```bash pnpm install --frozen-lockfile ``` 5. Avoid global installation where practical. Prefer a project-local, containerized, or otherwise sandboxed installation with minimal filesystem and network permissions. 6. Do not instruct users to install `@latest` as a troubleshooting step. Document a tested compatibility matrix and update the pinned version only after security review. 7. Document the exact system changes and privilege requirements of `agent-browser install --with-deps`. Explicitly discourage execution as root or through `sudo` unless strictly required and independently reviewed. 8. Add automated dependency provenance, vulnerability, and lockfile-integrity checks to the release process. ]]>
