T08 · Insecure Dependencies
- Location
skills.md:140- Finding
Unpinned Third-Party Dependencies Create a Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only Moss semantic search skill whose capabilities are disclosed and aligned with its stated purpose, with some operational cautions users should apply.
Install only in an environment where you are comfortable giving Moss SDK code access to the documents, queries, and Moss project credentials involved. Pin package versions, keep project keys in a secret manager or protected environment variables, review any automatic per-message retrieval for privacy implications, and confirm backups or retention requirements before using delete operations.
skills.md:140Unpinned Third-Party Dependencies Create a Supply-Chain Risk
The markdown describes deleting an index and all associated data, but does not include any caution, confirmation note, or warning about irreversible data loss. Because this skill documentation covers operations that can remove stored data, users should be explicitly warned before using them.
The skill advertises Delete Documents as a supported operation, but the description does not warn that stored documents may be permanently removed. For markdown skill descriptions, destructive data-affecting behaviors should be disclosed so users understand the risk.
The workflow recommends automatically sending each user message to a retrieval system and injecting results into LLM context without any privacy, consent, minimization, or sensitive-data handling guidance. In conversational systems, user messages frequently contain personal, confidential, or regulated data, so this pattern can lead to unnecessary collection, broader data exposure, and cross-context leakage if implemented naively.
The documentation instructs users to set MOSS_PROJECT_KEY and send x-project-key headers, but does not warn that these are sensitive credentials that must not be logged, committed, or exposed client-side. Since the markdown describes handling access keys, a basic user warning about secret management is warranted.
No suspicious patterns detected.