OmniFlow Studio - Connect Coding Agent to Google Flow extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: fipkgokjnfakoapmfelkdfcikigicpgk
Permissions (7)
- Browser debugger access
- Manage downloads
- View open tabs
Related extensions
AutoFlow PRO — Google Flow AutomationProductivity
FlowPilot - Google Flow Image AutomationProductivity
Flow Studio - AI Image and Video Generation for Google FlowProductivity
Flow Connector — connect your coding agent to Google Flow image & videoProductivity
FlowAGENTProductivity
Flow Connector - Agent Bridge for Google FlowProductivity
Frequently asked questions
Is OmniFlow Studio - Connect Coding Agent to Google Flow safe to use?
Our latest automated scan rates the Chrome listing of OmniFlow Studio - Connect Coding Agent to Google Flow at 72/100 (some risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does OmniFlow Studio - Connect Coding Agent to Google Flow require?
OmniFlow Studio - Connect Coding Agent to Google Flow requests 7 permissions. The most significant: Browser debugger access, Manage downloads, View open tabs. See the full breakdown in the security report.
Who develops OmniFlow Studio - Connect Coding Agent to Google Flow?
OmniFlow Studio - Connect Coding Agent to Google Flow is published by Sanify Digital. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 1.1.1
- Current listed version
- 1.1.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 2 critical and 4 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.