OpenFang

Open-source Agent Operating System

Agent Frameworks Rust Grade D Listed Apache-2.0
49.4/100
Rank #462 of 1283
Compare OpenFang

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-07-02 · 41d ago
Recent change
Rank +1

Is OpenFang safe? OpenFang scores 49.4/100 (Grade D), ranked #462 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 3.8/10; 26% of recent commits are signed; last pushed 2026-07-02. 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-10
Rank Moved
Rank dropped 32 spots (#427 → #459)
2026-08-08
Rank Moved
Rank dropped 109 spots (#317 → #426)
2026-07-29
Rank Moved
Rank dropped 10 spots (#314 → #324)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.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.
Refresh maintenance signals The repo was last pushed 41 days ago. Fresh activity helps separate stable projects from stale ones.
60.5
Activity sub-score · out of 100
#68

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-08-12 05:02 UTC · Repo last pushed 41 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
18.1k
Forks
2.3k
Last Push
2026-07-02
41 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
73
Rank Change
▲1
was #463

Analysis

HVTrust Dimensions vs Agent Frameworks

49.4 / 100 · 100.0% confidence

OpenFang Agent Frameworks average (118 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.0 / 25
2.1 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
11.7 / 17
in line with avg 11.5
Maintenance60% last-push freshness · 40% commit activity
9.3 / 20
5.0 below avg 14.3
AdoptionLog-scaled stars · package downloads
10.2 / 20
1.2 below avg 11.4

Activity Inputs

60.5 / 100
StarsRepository reach
25.5 / 30
FreshnessLast push recency
19.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
15.6 / 20

Supply Chain Trust

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

Is OpenFang safe?

Public trust evidence for OpenFang 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 OpenFang publish package provenance?
No published build provenance is currently detected for OpenFang. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does OpenFang have an OpenSSF Scorecard?
OpenFang has an OpenSSF Scorecard score of 3.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 OpenFang actively maintained?
Slowing down. Last push was 41 days ago — keep an eye on whether activity resumes.
What license does OpenFang use?
OpenFang ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are OpenFang's commits signed?
26% of the last 100 commits to OpenFang 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
OpenFang appears to expose MCP server capabilities.
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
high confidence
Extensions
Extension based 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

Maintain OpenFang?

For maintainers

HVTrust scores OpenFang 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 7Grade 2Listed 1Score 1
2026-08-10
Rank Moved
Rank dropped 32 spots (#427 → #459)
2026-08-08
Rank Moved
Rank dropped 109 spots (#317 → #426)
2026-07-29
Rank Moved
Rank dropped 10 spots (#314 → #324)
2026-07-15
Grade Changed
Trust grade C → D
2026-07-15
Rank Moved
Rank dropped 23 spots (#280 → #303)
2026-07-14
Rank Moved
Rank dropped 14 spots (#266 → #280)
2026-07-13
Rank Moved
Rank dropped 31 spots (#235 → #266)
2026-06-25
Grade Changed
Trust grade D → C
2026-06-25
Rank Moved
Rank rose 12 spots (#236 → #224)
2026-06-25
Activity Score Changed
Activity score up 6pts (60 → 66)
2026-06-24
Newly Listed
First tracked at rank #236

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 49.4 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/openfang.svg)](https://hvtracker.net/agents/openfang)
HTML:
<a href="https://hvtracker.net/agents/openfang"><img src="https://hvtracker.net/badge/openfang.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