updated 2026-10-17 20:06 UTC

Antigravity CLI

Repository by google-antigravity

Antigravity CLI brings the reasoning, execution, and orchestration capabilities of Antigravity agent harness directly into your terminal.

Coding Agents Listed Proprietary

Is Antigravity CLI safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.3 / 10
Provenance None
Signed commits 12%
Last push yesterday
Compare Antigravity CLI

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Antigravity CLI scores 43.7/100 (Grade D), ranked #1149 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.3/10; 12% of recent commits are signed; last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Antigravity 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.

Already done? Suggest a correctionAdd the trust badge
Tracking note

This GitHub repository is a public issue tracker for Antigravity, a closed-source product — it does not contain the product's source code. The OpenSSF Scorecard and license signals below describe that issue-tracker repo, not the shipped product.

Chain of custody

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

  1. Source Partly signed

    github.com/google-antigravity/antigravity-cli, last pushed 2026-10-16. 12% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.3/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 0
    Maintained 10
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions -1
    Vulnerabilities 10

  3. Published packages None

    No registry package. Antigravity CLI is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

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

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Antigravity 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 Antigravity CLI compares in Coding Agents

  1. #62 Grok CLI 46.3 +2.6
  2. #63 ZCode 44.8 +1.1
  3. #64 Antigravity CLI 43.7 this agent
  4. #65 Frontman 42.2 −1.5
  5. #66 Integuru 40.5 −3.2

Bars show each HVTrust score; the tick marks Antigravity CLI’s 43.7.

Where the 43.7 comes from

HVTrust dimensions vs the Coding Agents average

43.7 / 100 · 100.0% confidence

Antigravity CLI Coding Agents average (77 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.7 / 25
4.5 below avg 9.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
2.8 / 17
9.1 below avg 11.9
Maintenance60% last-push freshness · 40% commit activity
17.2 / 20
2.4 above avg 14.8
AdoptionLog-scaled stars · package downloads
8.2 / 20
3.9 below avg 12.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 10 spots (#1114 → #1124)
2026-10-01
Rank Moved
Rank dropped 11 spots (#1096 → #1107)
2026-09-23
Rank Moved
Rank dropped 628 spots (#451 → #1079)
Maintainer Checklist
Declare an open license Publish a clear OSI-approved license so usage and maintenance terms are independently verifiable.
Raise Scorecard signals Current OSSF Scorecard is 3.3/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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Antigravity CLI View Coding Agents Report missing data
73.0
Activity sub-score · out of 100
#64
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-17 20:06 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
2.6k
Forks
245
Last Push
2026-10-16
yesterday
Commits (4 wk)
20
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
709
Rank Change
▼2
was #1147

Analysis

Activity Inputs

73.0 / 100
StarsRepository reach
20.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
16.5 / 25
CommunityFork signal
11.1 / 20

Common questions about Antigravity CLI

Proprietary software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Antigravity CLI may have internal security practices not visible through public signals.
Public trust evidence for Antigravity CLI is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Antigravity CLI publish package provenance?
No published build provenance is currently detected for Antigravity 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 Antigravity CLI have an OpenSSF Scorecard?
Antigravity CLI has an OpenSSF Scorecard score of 3.3/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 Antigravity CLI actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Antigravity CLI use?
Antigravity CLI ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Antigravity CLI's commits signed?
11% of the last 100 commits to Antigravity 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Antigravity CLI?

For maintainers

HVTrust scores Antigravity 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

Reputation Timeline

Signal history
Rank 24
2026-10-09
Rank Moved
Rank dropped 10 spots (#1114 → #1124)
2026-10-01
Rank Moved
Rank dropped 11 spots (#1096 → #1107)
2026-09-23
Rank Moved
Rank dropped 628 spots (#451 → #1079)
2026-09-22
Rank Moved
Rank dropped 84 spots (#367 → #451)
2026-09-21
Rank Moved
Rank rose 710 spots (#1077 → #367)
2026-09-12
Rank Moved
Rank dropped 11 spots (#1060 → #1071)
2026-09-07
Rank Moved
Rank dropped 32 spots (#1010 → #1042)
2026-09-06
Rank Moved
Rank dropped 19 spots (#991 → #1010)
2026-09-05
Rank Moved
Rank dropped 48 spots (#943 → #991)
2026-09-04
Rank Moved
Rank dropped 27 spots (#916 → #943)
2026-09-03
Rank Moved
Rank dropped 42 spots (#874 → #916)
2026-09-02
Rank Moved
Rank rose 21 spots (#895 → #874)
2026-09-01
Rank Moved
Rank dropped 32 spots (#863 → #895)
2026-08-31
Rank Moved
Rank dropped 30 spots (#833 → #863)
2026-08-30
Rank Moved
Rank dropped 33 spots (#800 → #833)
2026-08-29
Rank Moved
Rank dropped 47 spots (#753 → #800)
2026-08-28
Rank Moved
Rank dropped 27 spots (#726 → #753)
2026-08-27
Rank Moved
Rank dropped 22 spots (#704 → #726)
2026-08-26
Rank Moved
Rank dropped 94 spots (#610 → #704)
2026-08-16
Rank Moved
Rank dropped 10 spots (#605 → #615)
2026-08-12
Rank Moved
Rank rose 36 spots (#635 → #599)
2026-08-10
Rank Moved
Rank dropped 25 spots (#614 → #639)
2026-08-08
Rank Moved
Rank dropped 217 spots (#393 → #610)
2026-07-29
Rank Moved
Rank dropped 10 spots (#372 → #382)
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Coding Agents

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON