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

What is the trust score for Eve?

Eve scores 63.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 4.7k GitHub stars and is categorized under Needs review.

Eve

vercel/eve

The Open Framework for Building Agents

Needs review TypeScript Grade C Listed Apache-2.0

63.2/100

Rank #275 of 1308

Compare Eve

How does it stack up against its Needs review 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 C · 2/5 signals

Last push

2026-08-19 · 0d ago

Recent change

Rank +3

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

Ranked neighbours in Needs review

#1 Turbovec — 64.8 (C) → #3 Obsidian Second Brain — 61.3 (C) → #4 ASM — 60.2 (C) → #5 Engram — 59.5 (C) →

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 15 spots (#260 → #275)

2026-08-17

Rank Moved

Rank rose 19 spots (#276 → #257)

2026-08-13

Rank Moved

Rank dropped 15 spots (#258 → #273)

Maintainer Checklist

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

Compare with Turbovec Get email alerts for Eve View Needs review Report missing data

84.4

Activity sub-score · out of 100

In Needs review

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

4.7k

Forks

466

Last Push

2026-08-19

today

Commits (4 wk)

519

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

250

Rank Change

▼15

was #260

Analysis

HVTrust Dimensions vs Needs review

63.2 / 100 · 100.0% confidence

Eve Needs review average (11 agents)

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

11.4 / 25

3.8 above avg 7.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

in line with avg 10.8

Transparency50% declared license · 50% OSSF Scorecard

12.8 / 17

0.5 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

5.3 above avg 14.7

AdoptionLog-scaled stars · package downloads

8.8 / 20

in line with avg 9.1

Activity Inputs

84.4 / 100

StarsRepository reach

22.0 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

12.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.1 / 10

OpenSSF Scorecard · scanned Aug 18, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 4

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 9

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is Eve safe?

Eve 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 Eve publish package provenance?

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

Does Eve have an OpenSSF Scorecard?

Eve has an OpenSSF Scorecard score of 5.1/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 Eve actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Eve use?

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

Are Eve's commits signed?

100% of the last 100 commits to Eve 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 Eve head-to-head

Eve vs Turbovec → Eve vs Obsidian Second Brain → Eve vs ASM →

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

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium confidence

Extensions

Extension based plugin/integration 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 Eve?

For maintainers

HVTrust scores Eve 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 15 spots (#260 → #275)

2026-08-17

Rank Moved

Rank rose 19 spots (#276 → #257)

2026-08-13

Rank Moved

Rank dropped 15 spots (#258 → #273)

2026-08-12

Rank Moved

Rank rose 15 spots (#273 → #258)

2026-08-10

Rank Moved

Rank dropped 17 spots (#253 → #270)

2026-08-08

Rank Moved

Rank dropped 55 spots (#197 → #252)

2026-07-14

Rank Moved

Rank dropped 10 spots (#164 → #174)

2026-07-13

Rank Moved

Rank dropped 20 spots (#144 → #164)

2026-06-19

Scorecard Added

OSSF Scorecard: 4.9/10

2026-06-19

Grade Changed

Trust grade D → C

2026-06-19

Rank Moved

Rank rose 85 spots (#221 → #136)

2026-06-19

HVTrust Changed

HVTrust up 36.0pts (25.2 → 61.2)

2026-06-18

Activity Score Changed

Activity score up 6pts (67 → 73)

2026-06-17

Newly Listed

First tracked at rank #219

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Needs review

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