T08 · Insecure Dependencies
- Location
SKILL.md:128- Finding
Unpinned Third-Party Package Installed Globally
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish and verify the expected package integrity hash or provenance before installation. 3. Link to the authoritative package source, publisher identity, and source commit corresponding to the pinned release. 4. Prefer bundling the required implementation in the Skill so that reviewers can inspect the code executed by the documented commands. 5. Review package lifecycle scripts and use `--ignore-scripts` if the package does not legitimately require installation scripts. 6. Avoid global installation where possible. Use a locked, project-local dependency with a committed lockfile and invoke the local executable. 7. Add automated dependency scanning and periodically review package ownership, release provenance, and advisories. 8. Correct the “zero-dependency” documentation so users understand that setup retrieves and executes a third-party package. ]]>
