T08 · Insecure Dependencies
- Location
SKILL.md:24- Finding
Unpinned Global Installation of a Third-Party npm Package
- Content
View full analysis
- Remediation
View remediation
``` 2. Verify the expected package publisher, registry URL, provenance, and integrity hash before installation. 3. Prefer a project-local, locked dependency over a global installation. 4. Execute the CLI from an isolated environment with narrowly scoped filesystem and network permissions. 5. Disable npm lifecycle scripts unless they are required and have been audited. 6. Require explicit user approval before installing or modifying software. 7. Validate the resolved executable path before invocation so that an unrelated or attacker-controlled binary cannot satisfy the `which` check. 8. Periodically audit the pinned package and update it only after reviewing the new release. ]]>
