T08 · Insecure Dependencies
- Location
SKILL.md:35- Finding
Unpinned External Package Installation and Dynamic Skill Loading
- Content
View full analysis
- Remediation
View remediation
add Lightprotocol/skills ``` 2. Pin the installed GitHub source to a reviewed commit SHA rather than a mutable branch or repository head. 3. Record and verify package integrity hashes, release signatures, or checksums before installation. 4. Do not automatically load `skills/ask-mcp`. Vendor it into the reviewed package or require a separate security review and explicit user approval before activation. 5. Treat MCP responses and remotely sourced Skill instructions as untrusted input. Do not permit them to override system constraints, expand filesystem scope, or initiate execution without confirmation. 6. Run installation and external Skill operations in a sandbox with: - Access limited to the intended project directory. - No wallet files, signing keys, tokens, or unrelated environment variables. - Restricted outbound network access. - No elevated operating-system privileges. 7. Change the workflow so local documentation and read-only repository inspection are attempted first. External Skill loading should be optional rather than a default recovery step. 8. Maintain a dependency lockfile or reviewed manifest documenting the exact npm package version, Git commit, external Skill revision, and MCP endpoint configuration. ]]>
