T08 · Insecure Dependencies
Warning
- Location
README.md:12- Finding
Unpinned Third-Party Package Execution During Installation
- Content
View full analysis
- Remediation
View remediation
add AntreasAntoniou/davinci-mode ``` 2. Where the tooling supports it, pin the skill source to an immutable commit or verified release rather than a mutable repository default branch. 3. Document the expected npm package name, publisher, version, and checksum or provenance information so users can verify what will execute. 4. Prefer an installation workflow that downloads and inspects the package before execution, or make the documented manual installation method the primary recommendation. 5. Use npm provenance, signed releases, lockfiles, and integrity verification where applicable. 6. Re-review and intentionally update pinned versions rather than automatically executing the latest available release. ]]>
