T08 · Insecure Dependencies
- Location
SKILL.md:297- Finding
Unpinned Third-Party Packages Create a Supply-Chain Execution Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This TTS skill appears purpose-related, but it needs review because it combines broad local execution/file authority, unpinned package installation, and unclear network/API-key disclosures.
Review before installing. Use an isolated virtual environment, avoid administrator/root installs, verify the Python packages and publishers yourself, and do not process sensitive text unless you confirm which providers run locally and which send content or credentials to third parties.
SKILL.md:297Unpinned Third-Party Packages Create a Supply-Chain Execution Risk
SKILL.md:23Skill Declares Unnecessarily Broad File and Command-Execution Capabilities
The documentation makes conflicting trust and privacy claims: it says the skill is free, offline, and requires no account, while later sections instruct users to obtain HuggingFace credentials and configure API keys. This can mislead users into exposing secrets or sending data over the network under false assumptions about local-only operation.
The skill documents translation, provider switching, and first-time voice downloads without clearly warning that user text or metadata may leave the local environment. In a TTS/translation skill, this context increases risk because users may process sensitive prompts, transcripts, or proprietary content and assume it stays local.
The FAQ minimizes network use by saying only first-time voice download needs connectivity, but setup sections describe HuggingFace registration and API-key configuration as required. Users may rely on the FAQ and unknowingly route content or credentials to third parties, creating privacy and secret-management risk through deceptive or inaccurate documentation.
The cleanup command is described as a convenience feature but lacks a prominent warning that it deletes cached audio files. This can cause unintended loss of locally stored outputs, which is a real safety issue, though limited in severity because it affects cache data rather than arbitrary files based on the provided documentation.
The documentation frames the skill as usable without an account, yet the security section warns about protecting account information. This is not merely incomplete documentation; it conveys conflicting user expectations about whether accounts are part of normal use.