T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Third-Party Global Installation Creates a Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
add ... ``` 2. Pin the remote source to an immutable commit hash or cryptographically verified release rather than a mutable repository reference. 3. Publish and verify checksums or signed provenance for the installed skill package. 4. Avoid global installation by default. Prefer a project-local installation with limited scope. 5. Review downloaded files before activation and display the resolved package version and source commit to the user. 6. Use lockfiles and automated dependency scanning for any packaged installation workflow. 7. Document how users can verify the source, version, integrity, and expected file list before running the installer. ]]>
