Is Gemini CLI safe to use?

Gemini CLI has an HVTrust score of 76.5/100 (Grade B), ranked #77 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Gemini CLI?

Gemini CLI scores 76.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 106.4k GitHub stars and is categorized under Coding Agents.

Gemini CLI

google-gemini/gemini-cli

An open-source AI agent that brings the power of Gemini directly into your terminal.

Coding Agents TypeScript Grade B Listed Apache-2.0

76.5/100

Rank #77 of 1204

Compare Gemini CLI

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-09 · 0d ago

Recent change

No recent signal change

Is Gemini CLI safe? Gemini CLI scores 76.5/100 (Grade B), ranked #77 of 1204 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.7/10; 100% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#7 Mistral Vibe — 84.1 (A) → #8 oh-my-pi — 83.0 (A) → #10 Open Interpreter — 74.6 (B) → #11 OpenHands — 73.1 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.7/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Gemini CLI View Coding Agents Report missing data

96.2

Activity sub-score · out of 100

In Coding Agents

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →

Activity & Reach

Stars

106.4k

Forks

14.4k

Last Push

2026-08-09

today

Commits (4 wk)

Downloads (7d)

594,518

npm

HN mentions (30d)

—

Open Issues

593

Rank Change

▲3

was #80

Analysis

HVTrust Dimensions vs Coding Agents

76.5 / 100 · 100.0% confidence

Gemini CLI Coding Agents average (65 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.9 / 25

3.0 above avg 7.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

12.5 / 17

1.3 above avg 11.2

Maintenance60% last-push freshness · 40% commit activity

19.0 / 20

3.9 above avg 15.1

AdoptionLog-scaled stars · package downloads

19.8 / 20

7.5 above avg 12.3

Activity Inputs

96.2 / 100

StarsRepository reach

30 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

21.9 / 25

CommunityFork signal

19.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.7 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 5

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 7

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Is Gemini CLI safe?

Public supply-chain signals for Gemini CLI are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Gemini CLI carries less obvious unverified-evidence risk than projects with thin signals.

Does Gemini CLI publish package provenance?

No published build provenance is currently detected for Gemini CLI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Gemini CLI have an OpenSSF Scorecard?

Gemini CLI has an OpenSSF Scorecard score of 4.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Gemini CLI actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Gemini CLI use?

Gemini CLI ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Gemini CLI's commits signed?

100% of the last 100 commits to Gemini CLI are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Gemini CLI appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration surface detected.

browser
code
shell

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Gemini CLI's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Gemini CLI?

For maintainers

HVTrust scores Gemini CLI from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Public Actions

Actions (30d)

112

Merged (30d)

104

Merge rate

93%

Top repos (sampled)

Action counts reflect activity on public repos where this agent left detectable fingerprints. Private repo usage is invisible. Counts are approximate (GitHub Search API caps at 1,000 results per query). Methodology described in the Provenance Profile spec.

Reputation Timeline

Signal history

2026-06-15

Rank Moved

Rank rose 10 spots (#65 → #55)

2026-06-15

Activity Score Changed

Activity score up 6pts (93 → 99)

2026-06-14

Activity Score Changed

Activity score down 5pts (98 → 93)

2026-06-05

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-06-05

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-06-05

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-05-30

Grade Changed

Trust grade C → B

2026-05-30

Rank Moved

Rank rose 26 spots (#63 → #37)

2026-05-30

HVTrust Changed

HVTrust up 3.9pts (67.0 → 70.9)

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (57.0 → 67.0)

2026-05-28

Activity Score Changed

Activity score up 25pts (74 → 99)

2026-05-27

Scorecard Added

OSSF Scorecard: 5.2/10

2026-05-27

Grade Changed

Trust grade D → C

2026-05-27

HVTrust Changed

HVTrust up 14.6pts (42.8 → 57.4)

2026-05-25

Rank Moved

Rank dropped 13 spots (#7 → #20)

2026-05-24

Newly Listed

First tracked at rank #7

GitHub → npm: @google/gemini-cli

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/gemini-cli.svg)](https://hvtracker.net/agents/gemini-cli)
            
HTML:
            <a href="https://hvtracker.net/agents/gemini-cli"><img src="https://hvtracker.net/badge/gemini-cli.svg" alt="HVTrust"></a>

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI · GitHub Search API (fingerprint actions)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON