T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Global Installation of a Mutable Third-Party Dependency
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish and verify the expected package digest, registry identity, and provenance before installation. 3. Prefer a project-local installation with a lockfile over a global installation where operationally possible. 4. Review the package and its dependency tree before approving version upgrades. 5. Disable npm lifecycle scripts during installation when the package's documented functionality permits it: ```bash npm install --global --ignore-scripts clawhub@ ``` 6. Execute the CLI with the least-privileged account and avoid using `sudo` or an administrator shell. 7. Require renewed review and explicit approval whenever the pinned version changes. ]]>
