T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned and Unverified Third-Party Dependencies
- Content
View full analysis
- Remediation
View remediation
`. - Prefer a project-local development dependency instead of a global installation. - Use a lockfile with integrity metadata. - Disable lifecycle scripts during installation when compatible with the package. - Document the official package owner and registry source. 3. Pin the MCP server to a specific reviewed release and provide its official HTTPS download URL. 4. Publish the expected SHA-256 checksum and require users to verify it before execution. 5. Require verification of the executable's digital signature and expected publisher identity. 6. Advise users to run the service as a non-administrative account with access limited to the image files and resources needed for publishing. 7. Document a secure upgrade process that requires review and integrity verification before changing dependency versions. ]]>
