Is auto-re-agent safe to use?

auto-re-agent has an HVTrust score of 51.2/100 (Grade C), ranked #892 of 1328 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 51.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.9k GitHub stars and is categorized under Security & Guardrails.

auto-re-agent

Dryxio/auto-re-agent

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

Security & Guardrails Python Grade C Listed MIT

51.2/100

Rank #892 of 1328

Compare auto-re-agent

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-09-09 · 11d ago

Recent change

No recent signal change

Is auto-re-agent safe? auto-re-agent scores 51.2/100 (Grade C), ranked #892 of 1328 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 →

Ranked neighbours in Security & Guardrails

#17 LLM Guard — 54.8 (C) → #18 pentest-ai — 54.4 (C) → #20 Llama Guard — 49.3 (D) → #21 AutoCVE — 47.5 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

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

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.

Compare with another agent Get email alerts for auto-re-agent View Security & Guardrails Report missing data

70.2

Activity sub-score · out of 100

#19

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

Activity & Reach

Stars

1.9k

Forks

196

Last Push

2026-09-09

11 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲4

was #896

Analysis

HVTrust Dimensions vs Security & Guardrails

51.2 / 100 · 100.0% confidence

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

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

5.6 / 25

4.6 below avg 10.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.3 below avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

11.9 / 17

0.9 below avg 12.8

Maintenance60% last-push freshness · 40% commit activity

16.5 / 20

1.0 above avg 15.5

AdoptionLog-scaled stars · package downloads

7.9 / 20

2.0 below avg 9.9

Activity Inputs

70.2 / 100

StarsRepository reach

19.7 / 30

FreshnessLast push recency

23.5 / 25

ActivityRecent commits

16.2 / 25

CommunityFork signal

10.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.0 / 10

OpenSSF Scorecard · scanned Sep 15, 2026

Signed Commits

12%

of last 100 commits verified

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

Is auto-re-agent safe?

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?

Maintained. Last push was 11 days ago.

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

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

2026-08-06

Newly Listed

First tracked at rank #500

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.3 · Raw JSON