Is OpenEvolve safe to use?

OpenEvolve has an HVTrust score of 50.2/100 (Grade C), ranked #464 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for OpenEvolve?

OpenEvolve scores 50.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 7.2k GitHub stars and is categorized under Agent Frameworks.

OpenEvolve

algorithmicsuperintelligence/openevolve

Open-source implementation of AlphaEvolve

Agent Frameworks Python Grade C Listed Apache-2.0

50.2/100

Rank #464 of 1308

Compare OpenEvolve

How does it stack up against its Agent Frameworks 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-07-18 · 32d ago

Recent change

Rank +3

Is OpenEvolve safe? OpenEvolve scores 50.2/100 (Grade C), ranked #464 of 1308 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 5.3/10; 41% of recent commits are signed; last pushed 2026-07-18. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#64 AgenticSeek — 51.3 (C) → #65 Mirascope — 50.7 (C) → #67 OpenFang — 49.6 (D) → #68 Qwen Agent — 49.3 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-19

Rank Moved

Rank dropped 14 spots (#450 → #464)

2026-08-13

Rank Moved

Rank dropped 17 spots (#423 → #440)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.3/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 32 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for OpenEvolve View Agent Frameworks Report missing data

58.1

Activity sub-score · out of 100

#66

In Agent Frameworks

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-08-19

Activity & Reach

Stars

7.2k

Forks

1.1k

Last Push

2026-07-18

32 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼14

was #450

Analysis

HVTrust Dimensions vs Agent Frameworks

50.2 / 100 · 100.0% confidence

OpenEvolve Agent Frameworks average (119 agents)

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

8.7 / 25

0.6 above avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

13.0 / 17

1.5 above avg 11.5

Maintenance60% last-push freshness · 40% commit activity

9.9 / 20

4.5 below avg 14.4

AdoptionLog-scaled stars · package downloads

9.3 / 20

2.0 below avg 11.3

Activity Inputs

58.1 / 100

StarsRepository reach

23.2 / 30

FreshnessLast push recency

20.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

14.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.3 / 10

OpenSSF Scorecard · scanned Aug 18, 2026

Signed Commits

41%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 7

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 9

Is OpenEvolve safe?

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

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

Does OpenEvolve have an OpenSSF Scorecard?

OpenEvolve 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 OpenEvolve actively maintained?

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

What license does OpenEvolve use?

OpenEvolve ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are OpenEvolve's commits signed?

41% of the last 100 commits to OpenEvolve 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 OpenEvolve'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-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

Maintain OpenEvolve?

For maintainers

HVTrust scores OpenEvolve 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-08-19

Rank Moved

Rank dropped 14 spots (#450 → #464)

2026-08-13

Rank Moved

Rank dropped 17 spots (#423 → #440)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Rank Moved

Rank rose 12 spots (#435 → #423)

2026-08-10

Rank Moved

Rank dropped 18 spots (#407 → #425)

2026-08-08

Rank Moved

Rank dropped 100 spots (#302 → #402)

2026-07-26

Rank Moved

Rank rose 16 spots (#279 → #263)

2026-07-15

Scorecard Added

OSSF Scorecard: 5.2/10

2026-07-15

Grade Changed

Trust grade D → C

2026-07-15

Rank Moved

Rank rose 137 spots (#412 → #275)

2026-07-15

HVTrust Changed

HVTrust up 33.0pts (20.4 → 53.4)

2026-07-14

Newly Listed

First tracked at rank #412

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

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