T08 · Insecure Dependencies
- Location
SKILL.md:46- Finding
Unpinned Third-Party Package Execution via npx
- Content
View full analysis
- Remediation
View remediation
install knowmine ``` 2. Do not use version ranges or distribution tags for security-sensitive installation instructions. 3. Where supported, verify the downloaded package using a published integrity hash, signature, provenance attestation, or trusted release checksum. 4. Document the expected package publisher, registry, exact version, and verification procedure so users can detect dependency confusion or registry substitution. 5. Review the selected package version, including lifecycle scripts and transitive dependencies, before recommending it. 6. Update the pinned version only through a controlled dependency-review process. 7. Advise users not to run the installer with administrative privileges and to use an isolated environment where practical. 8. In CI environments, use a lockfile or equivalent immutable dependency resolution and restrict installation-time network access to approved registries. ]]>
