T08 · Insecure Dependencies
Warning
- Location
SKILL.md:31- Finding
Unpinned Third-Party Package Execution Through npx
- Content
View full analysis
- Remediation
View remediation
domaindetails example.com ``` 2. Verify the pinned release's provenance, publisher identity, repository, and package contents before recommending it. 3. Prefer installing dependencies through a project manifest and committed lockfile rather than downloading and executing the latest release on demand. 4. Use npm integrity and provenance verification where supported, and monitor the package for publisher or ownership changes. 5. Configure automation to reject unexpected package versions and registry sources. 6. Prefer the documented HTTPS API examples when local third-party code execution is unnecessary. 7. Clearly disclose that `npx` may download and execute external code with the invoking user's permissions. ]]>
