T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Third-Party Dependencies
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Google Sheets automation guide, but users should apply least-privilege credentials and be careful with destructive sheet operations.
Before installing or using this skill, use a dedicated virtual environment, pin dependency versions for production, store the service-account key securely, share only the specific spreadsheets the service account needs, prefer narrower OAuth scopes where they work, and require explicit confirmation before clearing, overwriting, or deleting sheet data.
SKILL.md:10Unpinned Third-Party Dependencies
SKILL.md:25Excessive Google Drive OAuth Scope
The skill requests both Sheets and full Google Drive OAuth scopes even though the documented functionality is centered on spreadsheet access. Granting drive access expands the credential’s reach beyond the stated need, increasing blast radius if the service account key is exposed or the skill is misused. In this skill context, the issue is more dangerous because the examples normalize broad service-account permissions for automation workflows.
The documentation includes destructive operations such as ws.clear(), batch_clear, worksheet deletion, and overwrite patterns without any caution, confirmation guidance, or backup advice. In an agent skill, this can lead to accidental bulk data loss because users or downstream automation may invoke these examples directly against production spreadsheets. The skill context makes this more dangerous because it is explicitly designed for batch operations, so mistakes can affect large amounts of data quickly.
No suspicious patterns detected.