T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Third-Party npm Package Download and Execution
- Content
View full analysis
- Remediation
View remediation
" ``` 2. Pin the fallback command to the same reviewed version: ```bash npx --no-install @steipete/oracle@ --help ``` If local installation is not guaranteed, use an explicitly pinned installation process rather than resolving the latest release automatically. 3. Maintain a lockfile with integrity hashes where npm installation is performed as part of a managed project. 4. Verify package provenance, signatures, checksums, and publisher identity before updating the pinned version. 5. Review release changes and transitive dependency updates before accepting a new package version. 6. Avoid `npx -y` for security-sensitive workflows because it automatically approves downloading and running code. Require explicit user confirmation and clearly disclose that external package code will execute locally. 7. Where practical, install the reviewed package in an isolated environment with restricted filesystem access, limited credentials, and constrained network permissions. ]]>
