T08 · Insecure Dependencies
- Location
README.md:5- Finding
Unpinned Third-Party Package Execution Through npx
- Content
View full analysis
- Remediation
View remediation
install mcn-toolkit@ ``` 2. Document the authoritative registry, publisher identity, and expected package provenance so users can detect dependency-confusion or impersonation attempts. 3. Publish and verify package integrity information, such as registry integrity hashes, signed release attestations, or verifiable checksums. 4. Use a lockfile where installation occurs inside a managed project, and require reproducible dependency resolution. 5. Audit the pinned `clawhub` release, the installed `mcn-toolkit` artifact, lifecycle scripts, and transitive dependencies before recommending execution. 6. Prefer an installation process that separates package download and verification from execution. 7. Advise users to install under a least-privileged account and never run the command with administrator or root privileges unless explicitly required and independently justified. 8. Add automated dependency monitoring and release-signing controls so compromised or unexpectedly changed releases can be detected and revoked. ]]>
