T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned Third-Party Package Installation and Execution
- Content
View full analysis
- Remediation
View remediation
``` 2. Commit a `package.json` and `package-lock.json` containing the exact resolved version and npm integrity hash. 3. Replace implicit `npx` retrieval with execution of the pinned local binary: ```bash npm exec --offline -- vigil-agent-safety check --tool exec --params '{"command":"ls -la"}' ``` Alternatively, invoke `./node_modules/.bin/vigil-agent-safety` after a verified installation. 4. Audit or vendor the source code corresponding to the pinned package release so that the implementation included in the security boundary can be reviewed. 5. Install dependencies with lifecycle scripts disabled where compatible: ```bash npm ci --ignore-scripts ``` 6. Run the checker in a restricted environment with: - No unnecessary write access. - No access to SSH keys, cloud credentials, or unrelated secrets. - Denied outbound network access unless explicitly required. - A minimal environment-variable allowlist. - Child-process restrictions where supported. 7. Avoid passing secrets in tool parameters when they are not necessary for policy evaluation. Redact tokens, credentials, and sensitive request data before calling `checkAction`. 8. Add automated dependency review, integrity verification, and vulnerability monitoring for the pinned release. ]]>
