Reef

Infrastructure for continually self‑improving agents

Agent Frameworks Python Listed Apache-2.0

Is Reef safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.7 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare Reef
Suggest a correction

In detail: Reef scores 83.2/100 (Grade A), ranked #118 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.7/10; 100% of recent commits are signed; no published advisory affects its latest release (reef-infra); last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Reef 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.

Chain of custody

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

  1. Source Signed

    github.com/Human-Agent-Society/reef, Apache-2.0, last pushed 2026-10-16. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.7/10 (scanned Oct 5, 2026). The checks that decide who can get a change released:

    • Code Review6
    • Branch Protection4
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 6
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 3
  3. Published packages Linked and attested

    • PyPI reef-infra Source link points back to this repo Build provenance attested
  4. What you install today No known advisories

    Latest release checked: reef-infra 0.1.3. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-10-02 OSSF Scorecard: 4.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Reef’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.

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 Reef compares in Agent Frameworks

  1. #9 Agno 87.3 +4.1
  2. #10 Threadplane 85.2 +2.0
  3. #11 Reef 83.2 this agent
  4. #12 LangChain 82.7 −0.5
  5. #13 DawnAI 81.8 −1.4

Bars show each HVTrust score; the tick marks Reef’s 83.2.

Where the 83.2 comes from

HVTrust dimensions vs the Agent Frameworks average

83.2 / 100 · 100.0% confidence

Reef Agent Frameworks average (130 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.4 / 25
8.6 above avg 9.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.4 above avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.5 / 17
in line with avg 12.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.6 above avg 14.4
AdoptionLog-scaled stars · package downloads
12.4 / 20
1.1 above avg 11.3

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-15
Rank Moved
Rank rose 13 spots (#128 → #115)
2026-10-02
Scorecard Added
OSSF Scorecard: 4.8/10
2026-10-02
Grade Changed
Trust grade B → A
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.7/10. Tighten the weakest checks to improve public safety evidence.
86.6
Activity sub-score · out of 100
#11

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
7.6k
Forks
709
Last Push
2026-10-16
today
Commits (4 wk)
186
Downloads (7d)
188
pypi
HN mentions (30d)
—
Open Issues
69
Rank Change
▼3
was #115

Analysis

Activity Inputs

86.6 / 100
StarsRepository reach
23.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.3 / 20

Common questions about Reef

Public supply-chain signals for Reef are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Reef carries less obvious unverified-evidence risk than projects with thin signals.
Does Reef publish package provenance?
Yes. Reef's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Reef have an OpenSSF Scorecard?
Reef has an OpenSSF Scorecard score of 4.7/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 Reef actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Reef use?
Reef ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Reef's commits signed?
100% of the last 100 commits to Reef 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
None detected
No MCP server signal detected.
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
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Reef?

For maintainers

HVTrust scores Reef 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 3HVTrust 2Grade 2Listed 1Scorecard 1
2026-10-15
Rank Moved
Rank rose 13 spots (#128 → #115)
2026-10-02
Scorecard Added
OSSF Scorecard: 4.8/10
2026-10-02
Grade Changed
Trust grade B → A
2026-10-02
Rank Moved
Rank rose 147 spots (#256 → #109)
2026-10-02
HVTrust Changed
HVTrust up 9.8pts (73.5 → 83.3)
2026-10-01
Grade Changed
Trust grade D → B
2026-10-01
Rank Moved
Rank rose 752 spots (#1008 → #256)
2026-10-01
HVTrust Changed
HVTrust up 25.8pts (47.7 → 73.5)
2026-09-29
Newly Listed
First tracked at rank #1003

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 83.2 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/reef.svg)](https://hvtracker.net/agents/reef)
HTML:
<a href="https://hvtracker.net/agents/reef"><img src="https://hvtracker.net/badge/reef.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON