Is EverOS safe to use?

EverOS has an HVTrust score of 46.7/100 (Grade D), ranked #515 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for EverOS?

EverOS scores 46.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 12.2k GitHub stars and is categorized under Memory & Knowledge.

EverOS

EverMind-AI/EverOS

One portable memory layer for every AI agent: local-first, Markdown-native, user-owned, and self-evolving across apps, t

Memory & Knowledge Python Grade D Listed Apache-2.0

46.7/100

Rank #515 of 1308

Compare EverOS

How does it stack up against its Memory & Knowledge 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-08-17 · 2d ago

Recent change

Rank +1

Is EverOS safe? EverOS scores 46.7/100 (Grade D), ranked #515 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 7.1/10; 85% of recent commits are signed; last pushed 2026-08-17. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#32 LightMem — 49.9 (D) → #33 Memvid — 47.6 (D) → #35 ByteRover CLI — 46.6 (D) → #36 LycheeMemory — 44.3 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-08-17

Rank Moved

Rank rose 12 spots (#516 → #504)

2026-08-13

Rank Moved

Rank dropped 11 spots (#495 → #506)

2026-08-10

Rank Moved

Rank dropped 17 spots (#487 → #504)

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for EverOS View Memory & Knowledge Report missing data

84.1

Activity sub-score · out of 100

#34

In Memory & Knowledge

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

Activity & Reach

Stars

12.2k

Forks

891

Last Push

2026-08-17

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼8

was #507

Analysis

HVTrust Dimensions vs Memory & Knowledge

46.7 / 100 · 67.0% confidence

EverOS Memory & Knowledge average (44 agents)

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

13.1 / 25

3.2 above avg 9.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.3 below avg 12.1

Transparency50% declared license · 50% OSSF Scorecard

14.5 / 17

2.1 above avg 12.4

Maintenance60% last-push freshness · 40% commit activity

18.6 / 20

0.9 above avg 17.7

AdoptionLog-scaled stars · package downloads

9.8 / 20

3.8 below avg 13.6

Activity Inputs

84.1 / 100

StarsRepository reach

24.5 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

21.0 / 25

CommunityFork signal

13.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

7.1 / 10

OpenSSF Scorecard · scanned Aug 18, 2026

Signed Commits

85%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 8

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 1

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 0

Is EverOS safe?

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

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

Does EverOS have an OpenSSF Scorecard?

EverOS has an OpenSSF Scorecard score of 7.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 EverOS actively maintained?

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

What license does EverOS use?

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

Are EverOS's commits signed?

85% of the last 100 commits to EverOS 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

medium 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

2 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain EverOS?

For maintainers

HVTrust scores EverOS 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-17

Rank Moved

Rank rose 12 spots (#516 → #504)

2026-08-13

Rank Moved

Rank dropped 11 spots (#495 → #506)

2026-08-10

Rank Moved

Rank dropped 17 spots (#487 → #504)

2026-08-08

Rank Moved

Rank dropped 129 spots (#354 → #483)

2026-07-15

Scorecard Added

OSSF Scorecard: 6.3/10

2026-07-15

Rank Moved

Rank rose 67 spots (#400 → #333)

2026-07-15

HVTrust Changed

HVTrust up 22.4pts (22.6 → 45.0)

2026-07-14

Newly Listed

First tracked at rank #400

GitHub → PyPI: everos

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Memory & Knowledge

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