Archon

The first open-source harness builder for AI coding. Make AI coding deterministic and repeatable.

Coding Agents TypeScript Grade C Listed MIT
60.2/100
Rank #592 of 1328
Compare Archon

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-09-11 · 1d ago
Recent change
Rank +4

Is Archon safe? Archon scores 60.2/100 (Grade C), ranked #592 of 1328 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 4.8/10; 28% of recent commits are signed; last pushed 2026-09-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-09
Rank Moved
Rank dropped 26 spots (#558 → #584)
2026-09-08
Rank Moved
Rank dropped 10 spots (#548 → #558)
2026-09-07
Rank Moved
Rank dropped 26 spots (#522 → #548)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/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.
92.7
Activity sub-score · out of 100
#34

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-09-12 01:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-12

Activity & Reach

Stars
23.4k
Forks
3.5k
Last Push
2026-09-11
yesterday
Commits (4 wk)
1435
Downloads (7d)
HN mentions (30d)
Open Issues
294
Rank Change
▲1
was #593

Analysis

HVTrust Dimensions vs Coding Agents

60.2 / 100 · 100.0% confidence

Archon Coding Agents average (72 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.4 / 25
1.3 below avg 8.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
0.8 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
5.1 above avg 14.8
AdoptionLog-scaled stars · package downloads
10.5 / 20
1.6 below avg 12.1

Activity Inputs

92.7 / 100
StarsRepository reach
26.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
16.5 / 20

Supply Chain Trust

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

Is Archon safe?

Archon 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 Archon publish package provenance?
No published build provenance is currently detected for Archon. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Archon have an OpenSSF Scorecard?
Archon has an OpenSSF Scorecard score of 4.8/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 Archon actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Archon use?
Archon ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Archon's commits signed?
28% of the last 100 commits to Archon 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
Declared
MCP support appears present, but direct server implementation is less certain.
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 Archon?

For maintainers

HVTrust scores Archon 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 20Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-09
Rank Moved
Rank dropped 26 spots (#558 → #584)
2026-09-08
Rank Moved
Rank dropped 10 spots (#548 → #558)
2026-09-07
Rank Moved
Rank dropped 26 spots (#522 → #548)
2026-09-06
Rank Moved
Rank dropped 14 spots (#508 → #522)
2026-09-05
Rank Moved
Rank dropped 73 spots (#435 → #508)
2026-09-03
Rank Moved
Rank dropped 27 spots (#400 → #427)
2026-09-02
Rank Moved
Rank dropped 65 spots (#335 → #400)
2026-08-31
Rank Moved
Rank dropped 28 spots (#299 → #327)
2026-08-30
Rank Moved
Rank rose 10 spots (#309 → #299)
2026-08-29
Rank Moved
Rank dropped 16 spots (#293 → #309)
2026-08-26
Rank Moved
Rank dropped 21 spots (#263 → #284)
2026-08-24
Rank Moved
Rank dropped 10 spots (#248 → #258)
2026-08-22
Rank Moved
Rank rose 52 spots (#303 → #251)
2026-08-19
Rank Moved
Rank dropped 16 spots (#285 → #301)
2026-08-17
Rank Moved
Rank rose 20 spots (#306 → #286)
2026-08-13
Rank Moved
Rank dropped 18 spots (#281 → #299)
2026-08-12
Rank Moved
Rank rose 17 spots (#298 → #281)
2026-08-10
Rank Moved
Rank dropped 19 spots (#280 → #299)
2026-08-08
Rank Moved
Rank dropped 65 spots (#210 → #275)
2026-07-29
Scorecard Added
OSSF Scorecard: 4.2/10
2026-07-29
Grade Changed
Trust grade D → C
2026-07-29
Rank Moved
Rank rose 222 spots (#412 → #190)
2026-07-29
HVTrust Changed
HVTrust up 36.2pts (25.9 → 62.1)
2026-07-28
Newly Listed
First tracked at rank #412

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 60.2 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/archon.svg)](https://hvtracker.net/agents/archon)
HTML:
<a href="https://hvtracker.net/agents/archon"><img src="https://hvtracker.net/badge/archon.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.3 · Raw JSON