REA has an HVTrust score of 52.0/100 (Grade C), ranked #727 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for REA?

REA scores 52.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 395 GitHub stars and is categorized under Security & Guardrails.

REA

morluto/rea

Reverse engineer anything with agents, from app behavior down to native binaries.

Security & Guardrails TypeScript Grade C Listed MIT

52.0/100

Rank #727 of 1320

Compare REA

How does it stack up against its Security & Guardrails neighbours?

Pick any agent to compare →

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-08-29 · 6d ago

Recent change

Rank +8

Is REA safe? REA scores 52.0/100 (Grade C), ranked #727 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.3/10; 44% of recent commits are signed; last pushed 2026-08-29. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

#16 Llama Guard — 54.1 (C) → #17 pentest-ai — 54.1 (C) → #19 auto-re-agent — 48.2 (D) → #20 AutoCVE — 45.9 (D) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 30 spots (#697 → #727)

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-09-03

Grade Changed

Trust grade B → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.3/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for REA View Security & Guardrails Report missing data

60.7

Activity sub-score · out of 100

#18

In Security & Guardrails

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 →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

395

Forks

Last Push

2026-08-29

6 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼30

was #697

Analysis

HVTrust Dimensions vs Security & Guardrails

52.0 / 100 · 67.0% confidence

REA Security & Guardrails average (22 agents)

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

16.3 / 25

6.1 above avg 10.2

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.9 above avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

13.0 / 17

in line with avg 12.6

Maintenance60% last-push freshness · 40% commit activity

16.0 / 20

in line with avg 16.4

AdoptionLog-scaled stars · package downloads

6.2 / 20

3.4 below avg 9.6

Activity Inputs

60.7 / 100

StarsRepository reach

15.6 / 30

FreshnessLast push recency

24.2 / 25

ActivityRecent commits

13.9 / 25

CommunityFork signal

7.0 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.3 / 10

OpenSSF Scorecard · scanned Aug 30, 2026

Signed Commits

44%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 10

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 5

SAST 0

Security-Policy 4

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 4

Is REA safe?

Public trust evidence for REA 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 REA publish package provenance?

Yes. REA's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does REA have an OpenSSF Scorecard?

REA has an OpenSSF Scorecard score of 5.3/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 REA actively maintained?

Actively maintained. The repository was pushed to within the last 6 day(s).

What license does REA use?

REA ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are REA's commits signed?

44% of the last 100 commits to REA 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

REA 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

1 tags

Broad capability areas detected.

browser

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

How this surface has changed

Detected changes to REA'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-03

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain REA?

For maintainers

HVTrust scores REA 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-09-04

Rank Moved

Rank dropped 30 spots (#697 → #727)

2026-09-03

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-09-03

Grade Changed

Trust grade B → C

2026-09-03

Rank Moved

Rank dropped 599 spots (#98 → #697)

2026-09-03

HVTrust Changed

HVTrust down 26.7pts (78.9 → 52.2)

2026-08-31

Rank Moved

Rank dropped 12 spots (#87 → #99)

2026-08-28

Scorecard Added

OSSF Scorecard: 5.3/10

2026-08-28

Rank Moved

Rank rose 89 spots (#177 → #88)

2026-08-28

HVTrust Changed

HVTrust up 10.2pts (69.3 → 79.5)

2026-08-27

Rank Moved

Rank dropped 14 spots (#163 → #177)

2026-08-26

Rank Moved

Rank dropped 18 spots (#145 → #163)

2026-08-24

Rank Moved

Rank dropped 14 spots (#128 → #142)

2026-08-13

Rank Moved

Rank dropped 10 spots (#127 → #137)

2026-08-10

Newly Listed

First tracked at rank #135

GitHub → npm: rea-agents

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/rea.svg)](https://hvtracker.net/agents/rea)
            
HTML:
            <a href="https://hvtracker.net/agents/rea"><img src="https://hvtracker.net/badge/rea.svg" alt="HVTrust"></a>

Other agents in Security & Guardrails

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