Gemini CLI
64%
Total Score
caution
Active Google-backed maintenance is offset by high-confidence workflow findings involving pull-request automation and broad app permissions.
The audit is incomplete because only 30 of 47 workflows were analyzed. More importantly, high-confidence template-injection findings overlap with pull_request_target workflows, eval-pr also performs an untrusted checkout, and two workflows use blanket GitHub App permissions; these create meaningful CI supply-chain risk. Low-confidence cache-poisoning findings are secondary.
No build attestation or trusted-publisher identity is present, leaving release provenance less transparent despite the otherwise strong project backing.
The package has Google-domain publishing accounts and organization backing, which supports continuity. The outside-domain publishing account mrdoob (mrdoob.com) is an account-hygiene caution, not evidence of a small maintenance team.
Version 0.64.0 is not a stable major release and 85% of recent releases are prereleases, so consumers should expect more version churn than with a mature stable major.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-11004 @google/gemini-cli is vulnerable to Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in versions 0.0.1 - 0.39.0. | 0.0.1 - 0.39.0 | Critical |
AIKIDO-2026-10421 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. @google/gemini-cli is vulnerable to Prototype Pollution in versions 0.0.77 - 0.33.2. | 0.0.77 - 0.33.2 | Medium |
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.