EvoScientist

🔬 Harness Vibe Research with Self-evolving AI Scientists

Research & Data Python Grade C Listed Apache-2.0
60.7/100
Rank #599 of 1328
Compare EvoScientist

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-19 · 1d ago
Recent change
Rank +3

Is EvoScientist safe? EvoScientist scores 60.7/100 (Grade C), ranked #599 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 6.5/10; 87% of recent commits are signed; last pushed 2026-09-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-20
Rank Moved
Rank dropped 12 spots (#587 → #599)
2026-09-18
Rank Moved
Rank rose 11 spots (#599 → #588)
2026-09-17
Rank Moved
Rank rose 19 spots (#618 → #599)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/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.
76.9
Activity sub-score · out of 100
#12

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 →

Signals refreshed 2026-09-20 21:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars
4.9k
Forks
307
Last Push
2026-09-19
yesterday
Commits (4 wk)
28
Downloads (7d)
HN mentions (30d)
Open Issues
29
Rank Change
▼12
was #587

Analysis

HVTrust Dimensions vs Research & Data

60.7 / 100 · 100.0% confidence

EvoScientist Research & Data average (33 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.5 / 25
4.3 above avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.1 below avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
14.0 / 17
2.2 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
17.8 / 20
5.0 above avg 12.8
AdoptionLog-scaled stars · package downloads
8.9 / 20
2.0 below avg 10.9

Activity Inputs

76.9 / 100
StarsRepository reach
22.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
18.2 / 25
CommunityFork signal
11.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.5 / 10
OpenSSF Scorecard · scanned Sep 15, 2026
Signed Commits
87%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests 10
CII-Best-Practices 0
Code-Review 5
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 7
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 10

Is EvoScientist safe?

EvoScientist 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 EvoScientist publish package provenance?
No published build provenance is currently detected for EvoScientist. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does EvoScientist have an OpenSSF Scorecard?
EvoScientist has an OpenSSF Scorecard score of 6.5/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 EvoScientist actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does EvoScientist use?
EvoScientist ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are EvoScientist's commits signed?
87% of the last 100 commits to EvoScientist 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
low confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • search
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 EvoScientist?

For maintainers

HVTrust scores EvoScientist 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.

Reputation Timeline

Signal history
Rank 20Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-20
Rank Moved
Rank dropped 12 spots (#587 → #599)
2026-09-18
Rank Moved
Rank rose 11 spots (#599 → #588)
2026-09-17
Rank Moved
Rank rose 19 spots (#618 → #599)
2026-09-13
Rank Moved
Rank dropped 14 spots (#604 → #618)
2026-09-12
Rank Moved
Rank dropped 10 spots (#594 → #604)
2026-09-07
Rank Moved
Rank dropped 39 spots (#545 → #584)
2026-09-06
Rank Moved
Rank dropped 43 spots (#502 → #545)
2026-09-05
Rank Moved
Rank dropped 64 spots (#438 → #502)
2026-09-04
Rank Moved
Rank dropped 14 spots (#424 → #438)
2026-09-03
Rank Moved
Rank dropped 18 spots (#406 → #424)
2026-08-31
Rank Moved
Rank dropped 32 spots (#359 → #391)
2026-08-29
Scorecard Added
OSSF Scorecard: 6.6/10
2026-08-29
Grade Changed
Trust grade D → C
2026-08-29
Rank Moved
Rank rose 746 spots (#1109 → #363)
2026-08-29
HVTrust Changed
HVTrust up 39.1pts (21.8 → 60.9)
2026-08-28
Rank Moved
Rank dropped 30 spots (#1079 → #1109)
2026-08-27
Rank Moved
Rank dropped 17 spots (#1062 → #1079)
2026-08-26
Rank Moved
Rank dropped 83 spots (#979 → #1062)
2026-08-24
Rank Moved
Rank dropped 11 spots (#974 → #985)
2026-08-17
Rank Moved
Rank rose 20 spots (#994 → #974)
2026-08-16
Rank Moved
Rank dropped 35 spots (#959 → #994)
2026-08-10
Rank Moved
Rank dropped 59 spots (#897 → #956)
2026-08-08
Rank Moved
Rank dropped 414 spots (#475 → #889)
2026-08-06
Newly Listed
First tracked at rank #465

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 60.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/evoscientist.svg)](https://hvtracker.net/agents/evoscientist)
HTML:
<a href="https://hvtracker.net/agents/evoscientist"><img src="https://hvtracker.net/badge/evoscientist.svg" alt="HVTrust"></a>

Other agents in Research & Data

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