T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned npm CLI Dependency Creates a Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
" bins: [baijimu] ``` 2. Use a lockfile and registry-supported integrity hashes where the Skill installation mechanism supports them. 3. Verify package provenance, publisher ownership, signatures, and release attestations before approving upgrades. 4. Route dependency upgrades through code review and automated security scanning. 5. Disable npm lifecycle scripts during installation when they are not required; if they are required, review them before deployment. 6. Install and execute the CLI with a least-privileged account that does not unnecessarily expose production credentials. 7. Keep deployment credentials short-lived and scoped to only the required workspace, project, and operations. ]]>
