T08 · Insecure Dependencies
- Location
SKILL.md:20- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent and not malicious, but it asks users to install an unpinned package and store a Groq API key in a persistent plaintext workspace file.
Review before installing. Use a virtual environment and pinned dependency version for Pillow, and prefer a session-scoped environment variable or secret manager for the Groq key. Do not send secrets, customer data, unpublished proprietary material, or licensed content to Groq unless you are comfortable with that provider processing it.
SKILL.md:20Unpinned Third-Party Dependency Installation
SKILL.md:141API Key Stored in a Predictable Plaintext Workspace File
The skill directs users to place a Groq API key in a local .env file and send product prompts to Groq, but it does not disclose that prompts, listing copy, and possibly proprietary product materials will be transmitted to a third-party service. This creates a data exposure risk because users may unknowingly send confidential business information, unpublished content, or licensed material to an external API under that provider’s retention and usage policies.