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. Full methodology →
Signals refreshed2026-06-04 18:04 UTC·Repo last pushed yesterday
Activity & Reach
Stars
845
Forks
56
Last Push
2026-06-03
yesterday
Commits (4 wk)
9?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
253
Rank Change
NEW
Analysis
HVTrust Dimensions
16.4 / 100 · 50.0% confidence
Safety / IntegrityOSSF, provenance, signatures
1.1 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
0.0 / 17
MaintenanceFreshness and commits
13.9 / 20
AdoptionStars and downloads
7.0 / 20
Activity Inputs
63.3 / 100
StarsRepository reach
17.6 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
12.5 / 25
CommunityFork signal
8.2 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
22%
of last 100 commits verified
Is Antigravity CLI safe?
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?
No OpenSSF Scorecard data is currently published for Antigravity CLI. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
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?
22% 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Antigravity CLI?
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
