updated 2026-11-11 00:08 UTC

Reverify

Repository

Stop your AI from making things up — it proposes, deterministic tools decide, every claim checked against ground truth with evidence. Grounded facts and context survive resets. Reverse engineering is the proving ground. MCP server + CLI.

Observability & Evaluation Python Listed MIT

Is Reverify safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.7 / 10
Provenance None
Signed commits 14%
Last push 10d ago
Advisories None known
Compare Reverify

How does it stack up against its Observability & Evaluation neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Reverify scores 61.6/100 (Grade C), ranked #659 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.7/10; 14% of recent commits are signed; no published advisory affects its latest release (reverify); last pushed 2026-11-01. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Reverify 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 Partly signed

    github.com/2akouwu/reverify, MIT, last pushed 2026-11-01. 14% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protectionn/a
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies5
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection -1
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 5
    SAST 5
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 10

  3. Published packages Linked, not attested

    • PyPI reverify Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: reverify 0.10.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

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

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 Reverify’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 Reverify compares in Observability & Evaluation

  1. #15 Helicone 63.3 +1.7
  2. #16 cost-xray 61.7 +0.1
  3. #17 Reverify 61.6 this agent
  4. #18 OpenLIT 61.3 −0.3
  5. #19 Traceroot 60.7 −0.9

Bars show each HVTrust score; the tick marks Reverify’s 61.6.

Where the 61.6 comes from

HVTrust dimensions vs the Observability & Evaluation average

61.6 / 100 · 100.0% confidence

Reverify Observability & Evaluation average (28 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.1 / 25
2.4 below avg 11.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.3 below avg 13.1
Transparency50% declared license · 50% OSSF Scorecard
14.2 / 17
1.9 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
11.3 / 20
2.7 below avg 14.0
AdoptionLog-scaled stars · package downloads
10.5 / 20
2.6 below avg 13.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-10
Newly Listed
First tracked at rank #659
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.7/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.
Compare with another agent
View Observability & Evaluation Report missing data
53.7
Activity sub-score · out of 100
#17
In Observability & Evaluation

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 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-11-11 00:08 UTC · Repo last pushed 10 days ago

Activity & Reach

Stars
1.3k
Forks
259
Last Push
2026-11-01
10 days ago
Commits (4 wk)
0
Downloads (7d)
164
pypi
HN mentions (30d)
—
Open Issues
7
Rank Change
=
was #659

Analysis

Activity Inputs

53.7 / 100
StarsRepository reach
18.7 / 30
FreshnessLast push recency
23.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.2 / 20

Common questions about Reverify

Reverify 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 Reverify publish package provenance?
No published build provenance is currently detected for Reverify. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Reverify have an OpenSSF Scorecard?
Reverify has an OpenSSF Scorecard score of 6.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 Reverify actively maintained?
Maintained. Last push was 10 days ago.
What license does Reverify use?
Reverify ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Reverify's commits signed?
14% of the last 100 commits to Reverify 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
Reverify 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
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 Reverify?

For maintainers

HVTrust scores Reverify 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
Listed 1
2026-11-10
Newly Listed
First tracked at rank #659
GitHub → PyPI: reverify

Embed Badge Badge guide for maintainers →

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

Other agents in Observability & Evaluation

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