T08 · Insecure Dependencies
- Location
SKILL.md:100- Finding
Unpinned Dependency Installation Bypasses Managed Python Environment Protections
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to do invoice reporting locally, but its setup and export behavior need review before use.
Review before installing. Use a virtual environment instead of the provided system-level pip command, avoid running setup as an administrator, and store generated reports only in a private folder. Treat exported CSVs as sensitive billing data and be careful opening exports from invoice data you do not fully control.
SKILL.md:100Unpinned Dependency Installation Bypasses Managed Python Environment Protections
SKILL.md:324Spreadsheet Formula Injection in the Analytics CSV Export
The embedded code automatically writes a markdown report and CSV analytics export containing client names, emails, invoice status, amounts, and overdue information to local files without prominently warning users. In multi-user systems, shared workspaces, synced folders, backups, or CI/agent environments, these artifacts can persist and expose sensitive billing data beyond the user's expectations.
The security section states that all data stays on the machine and there is 'No transmission, no cloud' (L081-L083), presenting the skill as entirely local. However, the setup and manifest documentation require obtaining a LICENSE_KEY from ko-fi/openclaw-related external services (L015-L017, L089-L092), so the documentation overstates the skill's independence from external services. While the code itself does not transmit data, the documentation's absolute claim contradicts the operational dependency it describes.
No suspicious patterns detected.