oauth-automation
Audited by Socket on Mar 9, 2026
1 alert found:
Obfuscated FileThe skill's footprint is coherent with its stated purpose of OAuth token automation. It implements standard token refresh using the Google OAuth endpoint, uses the token for API calls, and provides options for real-time, scheduled, or hybrid token refresh workflows, including integration with n8n workflows. While the approach is sensible for developers needing automated token maintenance, there are notable security considerations: careful handling of tokens to avoid logging leakage, strict access control to the n8n API endpoints and environment-stored credentials, and ensuring that any code that updates workflows cannot be abused to inject malicious token data. Overall, the capability set is proportionate to the described use case, with moderate security considerations that should be mitigated via proper secrets management and access controls.