REA has an HVTrust score of 73.8/100 (Grade B), ranked #246 of 1325 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 73.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 415 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 Listed MIT

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

OSSF Scorecard 4.9 / 10

Provenance Attested

Signed commits 45%

Last push 18d ago

Compare REA

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

Pick any agent to compare →

Suggest a correction

In detail: REA scores 73.8/100 (Grade B), ranked #246 of 1325 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.9/10; 45% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How REA compares in Security & Guardrails

Bars show each HVTrust score; the tick marks REA’s 73.8.

Where the 73.8 comes from

HVTrust dimensions vs the Security & Guardrails average

73.8 / 100 · 100.0% confidence

REA Security & Guardrails average (22 agents)

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

15.9 / 25

5.3 above avg 10.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.9 above avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

12.7 / 17

in line with avg 12.9

Maintenance60% last-push freshness · 40% commit activity

12.7 / 20

2.6 below avg 15.3

AdoptionLog-scaled stars · package downloads

8.8 / 20

1.1 below avg 9.9

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-24

Rank Moved

Rank dropped 12 spots (#235 → #247)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.9/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 HOL Guard Get email alerts for REA View Security & Guardrails Report missing data

51.6

Activity sub-score · out of 100

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

415

Forks

Last Push

2026-09-08

18 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #246

Analysis

Activity Inputs

51.6 / 100

StarsRepository reach

15.7 / 30

FreshnessLast push recency

22.5 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

7.4 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

4.9 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

45%

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 0

Common questions about REA

REA 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 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 4.9/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?

Maintained. Last push was 18 days ago.

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?

45% 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.

Compare REA head-to-head

REA vs HOL Guard → REA vs DvalinCode → REA vs Guardrails AI →

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

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

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

Rank Moved

Rank dropped 12 spots (#235 → #247)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 659 spots (#894 → #235)

2026-09-23

HVTrust Changed

HVTrust up 47.5pts (26.9 → 74.4)

2026-09-22

Newly Listed

First tracked at rank #894

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-16

Rank Moved

Rank rose 19 spots (#252 → #233)

2026-09-13

Rank Moved

Rank dropped 12 spots (#237 → #249)

2026-09-12

Rank Moved

Rank dropped 21 spots (#216 → #237)

2026-09-09

Rank Moved

Rank dropped 42 spots (#163 → #205)

2026-09-07

Rank Moved

Rank dropped 12 spots (#144 → #156)

2026-09-05

Grade Changed

Trust grade C → B

2026-09-05

Rank Moved

Rank rose 583 spots (#727 → #144)

2026-09-05

HVTrust Changed

HVTrust up 26.5pts (52.0 → 78.5)

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