Case file No.043 · pypi · stdio

gflow-cli

io.github.ffroliva/gflow-cli · v0.86.0

Drive Google Flow from an agent: Veo video and Imagen image generation

Package ↗GitHub ↗Website ↗

Security score

96/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 0 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption6/10

1924 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v0.86.0)Oct 19, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is gflow-cli safe?

MCPWatch gives gflow-cli a heuristic security score of 96/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does gflow-cli have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package gflow-cli. That is not proof of safety.

When was gflow-cli last updated?

The latest registry version is 0.86.0, published Oct 18, 2026. The last push to ffroliva/gflow-cli was on Oct 19, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does gflow-cli use?

GitHub reports the license of ffroliva/gflow-cli as MIT.

Related servers

same publisher / similar score