T08 · Insecure Dependencies
- Location
SKILL.md:35- Finding
Unpinned npm Package Execution Through npx
- Content
View full analysis
- Remediation
View remediation
search "keyword" ``` 2. Prefer installing the reviewed version through a controlled dependency manifest and lockfile, then invoke the locked local binary: ```bash npm install --save-exact clawhub@ npx --no-install clawhub search "keyword" ``` 3. Document the authoritative package name, publisher, registry, and expected version so users can detect typosquatting or registry substitution. 4. Commit and verify an npm lockfile where the project model permits it. Use lockfile integrity metadata and a trusted registry. 5. Review package source, lifecycle scripts, ownership changes, and published artifacts before approving upgrades. Apply upgrades through an explicit review process rather than accepting the latest release automatically. 6. Run the CLI in a least-privilege, isolated environment without unrelated credentials or sensitive filesystem access, especially when evaluating a new version. 7. Consider disabling lifecycle scripts during installation where compatible, and verify package provenance or signatures when supported by the package distribution workflow. ]]>
