T08 · Insecure Dependencies
- Location
SKILL.md:21- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
- Remediation
View remediation
init ``` 3. Verify the package name, publisher identity, repository, provenance, and release signatures before recommending it. 4. Document the expected package registry and warn users against running the command with elevated privileges. 5. Use lockfiles and integrity metadata when integrating the package into a maintained project. 6. Periodically review the pinned version and update it only after security validation. 7. Where feasible, install and inspect the package without running lifecycle scripts before execution, and use a sandbox or restricted environment for initial validation. ]]>
