T09 · Insecure Skill Coding Practices
- Location
credentials.json:1- Finding
Hardcoded Google OAuth Client Credentials Distributed in Plaintext
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a coherent Google Workspace CLI helper, but it ships a real Google OAuth client credential file that is not disclosed or needed for the documented setup.
Review this before installing. The gog CLI use case is legitimate, but this package should not distribute a project-specific OAuth client secret. Prefer a version that removes credentials.json and requires you to supply your own Google OAuth client configuration. If you proceed, understand that authorizing Gmail, Calendar, Drive, Contacts, Sheets, and Docs grants broad access to your Google Workspace data and actions.
credentials.json:1Hardcoded Google OAuth Client Credentials Distributed in Plaintext
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Use `gog` for Gmail/Calendar/Drive/Contacts/Sheets/Docs. Requires OAuth setup.
Setup (once)
- `gog auth credentials /path/to/client_secret.json`
- `gog auth add you@gmail.com --services gmail,calendar,drive,contacts,sheets,docs`
- `gog auth list`