Back to plugin

Security audit

TangleClaw Google OAuth

Security checks for vulnerabilities and agentic risk

Overview

The plugin’s Google Workspace capabilities match its disclosures, with clear instructions requiring your permission for consequential actions.

Use a dedicated Google account and share only the files it needs. Protect the credential and token files, and keep the skill’s authorization rules active: API calls do not independently enforce confirmation. Sending, sharing, and editing affect real people and data. The README overstates token permanence; production tokens can still expire or become invalid under [Google’s documented conditions](https://developers.google.com/identity/protocols/oauth2#expiration).

Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Endor dependency reachability

Checked Nov 11, 2026 · 3:57 AM UTC

No reachable vulnerabilities reported

Endor dependency scan completed.