T08 · Insecure Dependencies
- Location
README.md:19- Finding
Installation from a Mutable Remote Source
- Content
View full analysis
- Remediation
View remediation
/SKILL.md ``` 2. Prefer signed, versioned release artifacts over direct installation from a development branch. 3. Publish a SHA-256 digest for every release and require the installer to verify it before loading the skill. 4. Use signed Git tags or artifact signatures and document how users or the installer can verify them. 5. Ensure the pinned skill and all referenced scripts belong to the same immutable release. 6. Retain the human-readable version number, commit hash, and checksum in the installation documentation to make the audited artifact identifiable. ]]>
