Is OpenFang safe to use?

OpenFang has an HVTrust score of 43.0/100 (Grade D), ranked #1165 of 1387 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for OpenFang?

OpenFang scores 43.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 18.2k GitHub stars and is categorized under Agent Frameworks.

OpenFang

Repository

Website

Open-source Agent Operating System

Agent Frameworks Rust Listed Apache-2.0

Is OpenFang safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.8 / 10

Provenance None

Signed commits 26%

Last push 136d ago

Compare OpenFang

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Suggest a correction

In detail: OpenFang scores 43.0/100 (Grade D), ranked #1165 of 1387 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 →

How OpenFang could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 3.8 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +11.0 → 54.0 C · #87 of 134
Sign every commit26% signed today +3.8 → 46.8 D · #106 of 134

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships OpenFang and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Partly signed

github.com/RightNow-AI/openfang, Apache-2.0, last pushed 2026-07-02. 26% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Nov 11, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

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
Published packages None

No registry package. OpenFang is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of OpenFang.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues OpenFang’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How OpenFang compares in Agent Frameworks

Bars show each HVTrust score; the tick marks OpenFang’s 43.0.

Where the 43.0 comes from

HVTrust dimensions vs the Agent Frameworks average

43.0 / 100 · 100.0% confidence

OpenFang Agent Frameworks average (134 agents)

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

6.0 / 25

4.0 below avg 10.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

11.7 / 17

0.7 below avg 12.4

Maintenance60% last-push freshness · 40% commit activity

2.9 / 20

12.1 below avg 15.0

AdoptionLog-scaled stars · package downloads

10.2 / 20

1.0 below avg 11.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

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 136 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent View Agent Frameworks Report missing data

47.4

Activity sub-score · out of 100

#113

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 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 →

Rank Trend

2026-09-29 2026-11-15

Activity & Reach

Stars

18.2k

Forks

2.3k

Last Push

2026-07-02

136 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1164

Analysis

Activity Inputs

47.4 / 100

StarsRepository reach

25.6 / 30

FreshnessLast push recency

6.1 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

15.6 / 20

Common questions about OpenFang

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 136 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

How this surface has changed

Detected changes to OpenFang'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-09-30

Activity Went Stale

No commits for 90 days

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-10-09

Rank Moved

Rank dropped 11 spots (#1073 → #1084)

2026-09-30

Activity Went Stale

No commits for 90 days

2026-09-25

Rank Moved

Rank dropped 11 spots (#1022 → #1033)

2026-09-23

Rank Moved

Rank dropped 612 spots (#406 → #1018)

2026-09-22

Rank Moved

Rank dropped 65 spots (#341 → #406)

2026-09-21

Rank Moved

Rank rose 677 spots (#1018 → #341)

2026-09-11

Rank Moved

Rank dropped 13 spots (#977 → #990)

2026-09-09

Rank Moved

Rank dropped 13 spots (#965 → #978)

2026-09-08

Rank Moved

Rank dropped 14 spots (#951 → #965)

2026-09-07

Rank Moved

Rank dropped 38 spots (#913 → #951)

2026-09-06

Rank Moved

Rank dropped 14 spots (#899 → #913)

2026-09-05

Rank Moved

Rank dropped 55 spots (#844 → #899)

2026-09-04

Rank Moved

Rank dropped 35 spots (#809 → #844)

2026-09-03

Rank Moved

Rank dropped 47 spots (#762 → #809)

2026-09-02

Rank Moved

Rank dropped 35 spots (#727 → #762)

2026-09-01

Rank Moved

Rank dropped 31 spots (#696 → #727)

2026-08-31

Rank Moved

Rank dropped 36 spots (#660 → #696)

2026-08-30

Rank Moved

Rank dropped 22 spots (#638 → #660)

2026-08-29

Rank Moved

Rank dropped 41 spots (#597 → #638)

2026-08-28

Rank Moved

Rank dropped 20 spots (#577 → #597)

2026-08-27

Rank Moved

Rank dropped 16 spots (#561 → #577)

2026-08-26

Rank Moved

Rank dropped 85 spots (#476 → #561)

2026-08-24

Rank Moved

Rank dropped 14 spots (#463 → #477)

2026-08-22

Rank Moved

Rank rose 13 spots (#478 → #465)

2026-08-19

Rank Moved

Rank dropped 20 spots (#457 → #477)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

OpenFang

How OpenFang could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How OpenFang compares in Agent Frameworks

Where the 43.0 comes from

HVTrust dimensions vs the Agent Frameworks average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about OpenFang

AI agent surface

Maintain OpenFang?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Frameworks