aeon has an HVTrust score of 25.6/100 (Grade D), ranked #834 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for aeon?

aeon scores 25.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 672 GitHub stars and is categorized under Agent Frameworks.

aeon

aeonfun/aeon

The most autonomous AI agent framework: runs unattended on GitHub Actions, self-healing skills, drives Claude Code, Grok

Agent Frameworks TypeScript Grade D Listed MIT

25.6/100

Rank #834 of 1308

Compare aeon

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-08-18 · 1d ago

Recent change

Provider Added +1

Is aeon safe? aeon scores 25.6/100 (Grade D), ranked #834 of 1308 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 96% of recent commits are signed; last pushed 2026-08-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#87 BabyAGI — 30.2 (D) → #88 JARVIS / HuggingGPT — 26.5 (D) → #90 QwenPaw — 25.0 (D) → #91 Chorus — 24.7 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-17

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-08-16

Rank Moved

Rank dropped 15 spots (#812 → #827)

2026-08-10

Rank Moved

Rank dropped 44 spots (#764 → #808)

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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 aeon View Agent Frameworks Report missing data

78.1

Activity sub-score · out of 100

#89

In Agent Frameworks

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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

672

Forks

241

Last Push

2026-08-18

yesterday

Commits (4 wk)

158

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼6

was #828

Analysis

HVTrust Dimensions vs Agent Frameworks

25.6 / 100 · 50.0% confidence

aeon Agent Frameworks average (119 agents)

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

4.8 / 25

3.3 below avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.0 below avg 11.5

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

5.5 above avg 14.4

AdoptionLog-scaled stars · package downloads

6.8 / 20

4.5 below avg 11.3

Activity Inputs

78.1 / 100

StarsRepository reach

17.0 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

96%

of last 100 commits verified

Is aeon safe?

Public trust evidence for aeon 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 aeon publish package provenance?

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

Does aeon have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for aeon. 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 aeon actively maintained?

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

What license does aeon use?

aeon ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are aeon's commits signed?

96% of the last 100 commits to aeon 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

aeon appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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

How this surface has changed

Detected changes to aeon'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-08-17

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-08-06

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

Maintain aeon?

For maintainers

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

2026-08-17

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-08-16

Rank Moved

Rank dropped 15 spots (#812 → #827)

2026-08-10

Rank Moved

Rank dropped 44 spots (#764 → #808)

2026-08-08

Rank Moved

Rank dropped 326 spots (#433 → #759)

2026-08-06

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-03

Newly Listed

First tracked at rank #426

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

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