updated 2026-08-12 05:02 UTC

REA

morluto/rea

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

Security & Guardrails TypeScript Grade B Listed MIT
70.5/100
Rank #135 of 1283
Compare REA

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-11 · 1d ago
Recent change
New

Is REA safe? REA scores 70.5/100 (Grade B), ranked #135 of 1283 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; no OSSF Scorecard result yet; 44% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Security & Guardrails

#2 Guardrails AI — 81.8 (A) → #3 NeMo Guardrails — 72.0 (B) → #5 Snyk Agent Scan — 64.0 (C) → #6 PentAGI — 63.8 (C) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #135
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with DvalinCode Get email alerts for REA View Security & Guardrails Report missing data
69.5
Activity sub-score · out of 100
#4
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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
167
Forks
20
Last Push
2026-08-11
yesterday
Commits (4 wk)
591
Downloads (7d)
528
npm
HN mentions (30d)
—
Open Issues
50
Rank Change
▼1
was #134

Analysis

HVTrust Dimensions vs Security & Guardrails

70.5 / 100 · 100.0% confidence

REA Security & Guardrails average (19 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.7 / 25
1.4 above avg 8.3
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.1 above avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.2 below avg 11.7
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
3.6 above avg 16.3
AdoptionLog-scaled stars · package downloads
9.0 / 20
1.0 below avg 10.0

Activity Inputs

69.5 / 100
StarsRepository reach
13.4 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
6.1 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
44%
of last 100 commits verified

Is REA safe?

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?
No OpenSSF Scorecard data is currently published for REA. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is REA actively maintained?
Actively maintained. The repository was pushed to within the last 1 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.

Compare REA head-to-head

REA vs DvalinCode → REA vs Guardrails AI → REA vs NeMo Guardrails →

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
Declared
Declared plugin/integration surface 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

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
Listed 1
2026-08-10
Newly Listed
First tracked at rank #135
GitHub → npm: rea-agents

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 70.5 Grade B
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON