Is auto-re-agent safe to use?

auto-re-agent has an HVTrust score of 43.1/100 (Grade D), ranked #1153 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for auto-re-agent?

auto-re-agent scores 43.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.4k GitHub stars and is categorized under Security & Guardrails.

auto-re-agent

Repository

Reconstruct and validate C/C++ code from compiled programs with AI.

Security & Guardrails Python Listed MIT

Is auto-re-agent safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.0 / 10

Provenance None

Signed commits 12%

Last push 57d ago

Compare auto-re-agent

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

Pick any agent to compare →

Suggest a correction

In detail: auto-re-agent scores 43.1/100 (Grade D), ranked #1153 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.0/10; 12% of recent commits are signed; last pushed 2026-09-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How auto-re-agent 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.

Raise the OSSF Scorecard from 4.0 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Contributors 0 +10.5 → 53.6 C · #17 of 26
Sign every commit12% signed today +4.4 → 47.5 D · #23 of 26

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Partly signed

github.com/Dryxio/reagent, MIT, last pushed 2026-09-09. 12% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.0/10 (scanned Nov 3, 2026). The checks that decide who can get a change released:
- Code Review1
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies1
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 5

CII-Best-Practices 0

Code-Review 1

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 1

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10
Published packages None

No registry package. auto-re-agent is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-08-26 OSSF Scorecard: 4.1/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues auto-re-agent’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 auto-re-agent compares in Security & Guardrails

Bars show each HVTrust score; the tick marks auto-re-agent’s 43.1.

Where the 43.1 comes from

HVTrust dimensions vs the Security & Guardrails average

43.1 / 100 · 100.0% confidence

auto-re-agent Security & Guardrails average (26 agents)

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

5.6 / 25

4.8 below avg 10.4

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.4 below avg 12.2

Transparency50% declared license · 50% OSSF Scorecard

11.9 / 17

0.8 below avg 12.7

Maintenance60% last-push freshness · 40% commit activity

8.2 / 20

6.7 below avg 14.9

AdoptionLog-scaled stars · package downloads

8.1 / 20

1.9 below avg 10.0

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-10

Rank Moved

Rank dropped 69 spots (#1039 → #1108)

2026-10-10

Activity Score Changed

Activity score down 9pts (60 → 52)

2026-10-09

Rank Moved

Rank dropped 78 spots (#961 → #1039)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.0/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.

Refresh maintenance signals The repo was last pushed 57 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent View Security & Guardrails Report missing data

48.7

Activity sub-score · out of 100

#24

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 D 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-09-29 2026-11-05

Activity & Reach

Stars

2.4k

Forks

253

Last Push

2026-09-09

57 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #1151

Analysis

Activity Inputs

48.7 / 100

StarsRepository reach

20.3 / 30

FreshnessLast push recency

17.1 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

11.2 / 20

Common questions about auto-re-agent

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

No published build provenance is currently detected for auto-re-agent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does auto-re-agent have an OpenSSF Scorecard?

auto-re-agent has an OpenSSF Scorecard score of 4.0/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 auto-re-agent actively maintained?

Slowing down. Last push was 57 days ago — keep an eye on whether activity resumes.

What license does auto-re-agent use?

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

Are auto-re-agent's commits signed?

12% of the last 100 commits to auto-re-agent 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

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 auto-re-agent'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

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

Maintain auto-re-agent?

For maintainers

HVTrust scores auto-re-agent 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-10-10

Rank Moved

Rank dropped 69 spots (#1039 → #1108)

2026-10-10

Activity Score Changed

Activity score down 9pts (60 → 52)

2026-10-09

Rank Moved

Rank dropped 78 spots (#961 → #1039)

2026-10-09

Activity Score Changed

Activity score down 7pts (68 → 60)

2026-10-07

Grade Changed

Trust grade C → D

2026-09-30

Rank Moved

Rank dropped 12 spots (#928 → #940)

2026-09-25

Rank Moved

Rank dropped 14 spots (#908 → #922)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 434 spots (#468 → #902)

2026-09-23

HVTrust Changed

HVTrust up 7.6pts (43.4 → 51.0)

2026-09-22

Newly Listed

First tracked at rank #468

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank dropped 10 spots (#860 → #870)

2026-09-10

Rank Moved

Rank dropped 10 spots (#850 → #860)

2026-09-09

Grade Changed

Trust grade D → C

2026-09-09

Rank Moved

Rank rose 117 spots (#967 → #850)

2026-09-09

HVTrust Changed

HVTrust up 4.8pts (47.2 → 52.0)

2026-09-09

Activity Score Changed

Activity score up 14pts (58 → 71)

2026-09-08

Rank Moved

Rank dropped 14 spots (#953 → #967)

2026-09-07

Rank Moved

Rank dropped 35 spots (#918 → #953)

2026-09-06

Rank Moved

Rank dropped 12 spots (#906 → #918)

2026-09-05

Rank Moved

Rank dropped 69 spots (#837 → #906)

2026-09-04

Rank Moved

Rank rose 77 spots (#914 → #837)

2026-09-04

HVTrust Changed

HVTrust up 4.0pts (44.2 → 48.2)

2026-09-04

Activity Score Changed

Activity score up 10pts (48 → 58)

2026-09-03

Rank Moved

Rank dropped 51 spots (#863 → #914)

2026-09-02

Rank Moved

Rank dropped 42 spots (#821 → #863)

2026-09-01

Rank Moved

Rank dropped 32 spots (#789 → #821)

2026-08-31

Rank Moved

Rank dropped 36 spots (#753 → #789)

2026-08-30

Rank Moved

Rank dropped 23 spots (#730 → #753)

2026-08-29

Rank Moved

Rank dropped 51 spots (#679 → #730)

2026-08-28

Rank Moved

Rank dropped 24 spots (#655 → #679)

2026-08-27

Rank Moved

Rank dropped 18 spots (#637 → #655)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.1/10

2026-08-26

Rank Moved

Rank rose 563 spots (#1200 → #637)

2026-08-26

HVTrust Changed

HVTrust up 27.3pts (17.4 → 44.7)

2026-08-22

Rank Moved

Rank dropped 25 spots (#1172 → #1197)

2026-08-18

Rank Moved

Rank dropped 13 spots (#1154 → #1167)

2026-08-16

Rank Moved

Rank dropped 47 spots (#1108 → #1155)

2026-08-14

Rank Moved

Rank dropped 32 spots (#1075 → #1107)

2026-08-10

Rank Moved

Rank dropped 62 spots (#1012 → #1074)

2026-08-08

Rank Moved

Rank dropped 515 spots (#490 → #1005)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Security & Guardrails

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

auto-re-agent

How auto-re-agent could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How auto-re-agent compares in Security & Guardrails

Where the 43.1 comes from

HVTrust dimensions vs the Security & Guardrails average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about auto-re-agent

AI agent surface

Maintain auto-re-agent?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Security & Guardrails