Is Gemini CLI safe to use?

Gemini CLI has an HVTrust score of 76.6/100 (Grade B), ranked #211 of 1371 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.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 107.3k GitHub stars and is categorized under Coding Agents.

Gemini CLI

Repository

Website

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

Coding Agents TypeScript Listed Apache-2.0

Is Gemini CLI safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.7 / 10

Provenance None

Signed commits 100%

Last push yesterday

Advisories None known

Compare Gemini CLI

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Gemini CLI scores 76.6/100 (Grade B), ranked #211 of 1371 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; no published advisory affects its latest release (@google/gemini-cli); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Gemini CLI could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Publish build provenance for its packagesnpm publish --provenance from CI +12.4 → 89.0 A · #4 of 77
Raise the OSSF Scorecard from 4.7 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Dangerous-Workflow 0 +8.3 → 84.9 A · #8 of 77

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Gemini CLI and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/google-gemini/gemini-cli, Apache-2.0, last pushed 2026-10-08. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.7/10 (scanned Sep 29, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection0
- Signed Releases0
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies7
All 18 Scorecard checks

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 9

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages Linked, not attested
- npm @google/gemini-cli Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: @google/gemini-cli 0.63.0. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Gemini CLI.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions
Community mentions (missing)

Verify this score yourself

Every build re-issues Gemini CLI’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Gemini CLI compares in Coding Agents

Bars show each HVTrust score; the tick marks Gemini CLI’s 76.6.

Where the 76.6 comes from

HVTrust dimensions vs the Coding Agents average

76.6 / 100 · 100.0% confidence

Gemini CLI Coding Agents average (77 agents)

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

10.9 / 25

2.1 above avg 8.8

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

0.9 above avg 11.6

Maintenance60% last-push freshness · 40% commit activity

19.3 / 20

4.9 above avg 14.4

AdoptionLog-scaled stars · package downloads

19.6 / 20

7.7 above avg 11.9

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-23

Rank Moved

Rank dropped 127 spots (#85 → #212)

2026-09-21

Rank Moved

Rank rose 131 spots (#216 → #85)

2026-09-11

Rank Moved

Rank dropped 11 spots (#197 → #208)

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

97.5

Activity sub-score · out of 100

#10

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 →

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars

107.3k

Forks

14.7k

Last Push

2026-10-08

yesterday

Commits (4 wk)

Downloads (7d)

454,428

npm

HN mentions (30d)

—

Open Issues

504

Rank Change

▼6

was #205

Analysis

Activity Inputs

97.5 / 100

StarsRepository reach

30 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

23.1 / 25

CommunityFork signal

19.4 / 20

Common questions about Gemini CLI

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

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)

Merged (30d)

Merge rate

88%

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-09-23

Rank Moved

Rank dropped 127 spots (#85 → #212)

2026-09-21

Rank Moved

Rank rose 131 spots (#216 → #85)

2026-09-11

Rank Moved

Rank dropped 11 spots (#197 → #208)

2026-09-07

Rank Moved

Rank dropped 18 spots (#181 → #199)

2026-09-05

Rank Moved

Rank dropped 38 spots (#139 → #177)

2026-08-31

Rank Moved

Rank dropped 18 spots (#103 → #121)

2026-08-26

Rank Moved

Rank dropped 10 spots (#83 → #93)

GitHub → Website → 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.4 · Raw JSON

Gemini CLI

How Gemini CLI could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Gemini CLI compares in Coding Agents

Where the 76.6 comes from

HVTrust dimensions vs the Coding Agents average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Gemini CLI

AI agent surface

Maintain Gemini CLI?

Public Actions

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Coding Agents