T08 · Insecure Dependencies
- Location
reference/shared.md:11- Finding
Unpinned Global Installation of a Third-Party CLI Package
- Content
View full analysis
- Remediation
View remediation
``` 2. Document the expected npm registry and reject installation from untrusted registry overrides. 3. Verify the package tarball against a publisher-provided integrity value or cryptographic signature before installation. 4. Prefer a project-local dependency with a committed lockfile instead of a global installation. 5. Perform dependency and provenance checks whenever the pinned version is upgraded. 6. Avoid running npm with administrative privileges. If global installation is necessary, use a user-owned installation prefix. 7. Consider executing the CLI in a restricted environment with only the filesystem and network access required for media processing. ]]>
