T08 · Insecure Dependencies
- Location
SKILL.md:24- Finding
Automatic Execution of an Unpinned npm Package
- Content
View full analysis
- Remediation
View remediation
``` 2. Verify the selected release and its transitive dependencies through a committed lockfile and npm integrity hashes. 3. Require explicit user approval before downloading or executing software that is not already installed. 4. Prefer a trusted, locally installed binary whose version is checked against an allowlist. 5. Run package installation and rendering in a sandbox with: - Restricted filesystem access. - Minimal environment variables. - Limited network access. - No elevated privileges. 6. Establish a controlled update process in which new package versions are reviewed and tested before changing the pinned version. 7. Consider using a trusted internal registry or verified package mirror to reduce exposure to public-registry compromise. ]]>
