T08 · Insecure Dependencies
- Location
SKILL.md:103- Finding
Unpinned Global npm Package Installation Creates a Supply-Chain Execution Risk
- Content
View full analysis
- Remediation
View remediation
``` 2. Document the expected package version and published integrity digest. 3. Verify npm provenance, package ownership, and integrity before installation. 4. Review release notes and package lifecycle scripts before upgrading. 5. Avoid automatically reinstalling the Gateway immediately after an unreviewed upgrade. 6. Validate the installed executable and package version before registering the service: ```bash which openclaw openclaw --version npm list -g --depth=0 openclaw ``` 7. Where feasible, test the pinned release in an isolated environment before deploying it as a persistent Gateway service. ]]>
