Google AX

An open source distributed agent runtime

Agent Frameworks Go Grade C Listed Apache-2.0
58.0/100
Rank #366 of 1283
Compare Google AX

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-13 · 2d ago
Recent change
Rank +3

Is Google AX safe? Google AX scores 58.0/100 (Grade C), ranked #366 of 1283 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 5.4/10; 1% of recent commits are signed; last pushed 2026-08-13. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-13
Rank Moved
Rank dropped 20 spots (#344 → #364)
2026-08-12
Rank Moved
Rank rose 35 spots (#379 → #344)
2026-08-10
Rank Moved
Rank dropped 19 spots (#357 → #376)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.4/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.
74.7
Activity sub-score · out of 100
#53

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-08-15 09:32 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars
2.0k
Forks
114
Last Push
2026-08-13
2 days ago
Commits (4 wk)
43
Downloads (7d)
HN mentions (30d)
Open Issues
34
Rank Change
=
was #366

Analysis

HVTrust Dimensions vs Agent Frameworks

58.0 / 100 · 100.0% confidence

Google AX Agent Frameworks average (118 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.8 / 25
1.4 below avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
13.1 / 17
1.5 above avg 11.6
Maintenance60% last-push freshness · 40% commit activity
18.4 / 20
4.2 above avg 14.2
AdoptionLog-scaled stars · package downloads
7.9 / 20
3.5 below avg 11.4

Activity Inputs

74.7 / 100
StarsRepository reach
19.7 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
20.5 / 25
CommunityFork signal
9.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.4 / 10
OpenSSF Scorecard · scanned Aug 14, 2026
Signed Commits
1%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 1
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 6
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 7

Is Google AX safe?

Google AX has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Google AX publish package provenance?
No published build provenance is currently detected for Google AX. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Google AX have an OpenSSF Scorecard?
Google AX has an OpenSSF Scorecard score of 5.4/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 Google AX actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Google AX use?
Google AX ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Google AX's commits signed?
1% of the last 100 commits to Google AX 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
medium confidence
Implemented
Google AX 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.
Credential signal: API keys or service config markers documented.
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 Google AX?

For maintainers

HVTrust scores Google AX 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.

Reputation Timeline

Signal history
Rank 5Listed 1HVTrust 1Grade 1Scorecard 1
2026-08-13
Rank Moved
Rank dropped 20 spots (#344 → #364)
2026-08-12
Rank Moved
Rank rose 35 spots (#379 → #344)
2026-08-10
Rank Moved
Rank dropped 19 spots (#357 → #376)
2026-08-08
Rank Moved
Rank dropped 89 spots (#264 → #353)
2026-07-29
Scorecard Added
OSSF Scorecard: 5.4/10
2026-07-29
Grade Changed
Trust grade D → C
2026-07-29
Rank Moved
Rank rose 181 spots (#418 → #237)
2026-07-29
HVTrust Changed
HVTrust up 34.6pts (23.9 → 58.5)
2026-07-28
Newly Listed
First tracked at rank #418

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 58.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/google-ax.svg)](https://hvtracker.net/agents/google-ax)
HTML:
<a href="https://hvtracker.net/agents/google-ax"><img src="https://hvtracker.net/badge/google-ax.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

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.3 · Raw JSON