Eliza

Open source agentic operating system

Agent Frameworks TypeScript Grade B Listed MIT
65.4/100
Rank #229 of 1308
Compare Eliza

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-25 · 0d ago
Recent change
Rank +2

Is Eliza safe? Eliza scores 65.4/100 (Grade B), ranked #229 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.1/10; 16% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-24
Rank Moved
Rank dropped 15 spots (#215 → #230)
2026-08-22
Rank Moved
Rank rose 19 spots (#234 → #215)
2026-08-19
Rank Moved
Rank dropped 13 spots (#214 → #227)
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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
93.2
Activity sub-score · out of 100
#35

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-25 08:32 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars
19.2k
Forks
5.7k
Last Push
2026-08-25
today
Commits (4 wk)
8230
Downloads (7d)
18,459
npm
HN mentions (30d)
Open Issues
471
Rank Change
▲1
was #230

Analysis

HVTrust Dimensions vs Agent Frameworks

65.4 / 100 · 100.0% confidence

Eliza Agent Frameworks average (119 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.2 / 25
0.9 below 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
12.8 / 17
1.3 above avg 11.5
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.8 above avg 14.2
AdoptionLog-scaled stars · package downloads
16.0 / 20
4.7 above avg 11.3

Activity Inputs

93.2 / 100
StarsRepository reach
25.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.1 / 10
OpenSSF Scorecard · scanned Jul 11, 2026 (refresh pending)
Signed Commits
16%
of last 100 commits verified
Binary-Artifacts 0
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 2
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 10
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 2
SAST 7
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Eliza safe?

Eliza 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 Eliza publish package provenance?
No published build provenance is currently detected for Eliza. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Eliza have an OpenSSF Scorecard?
Eliza 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 Eliza actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Eliza use?
Eliza ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Eliza's commits signed?
16% of the last 100 commits to Eliza 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: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Eliza?

For maintainers

HVTrust scores Eliza 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 22HVTrust 2Grade 1Scorecard 1
2026-08-24
Rank Moved
Rank dropped 15 spots (#215 → #230)
2026-08-22
Rank Moved
Rank rose 19 spots (#234 → #215)
2026-08-19
Rank Moved
Rank dropped 13 spots (#214 → #227)
2026-08-17
Rank Moved
Rank rose 14 spots (#228 → #214)
2026-08-13
Rank Moved
Rank dropped 16 spots (#206 → #222)
2026-08-12
Rank Moved
Rank rose 17 spots (#223 → #206)
2026-08-10
Rank Moved
Rank dropped 16 spots (#206 → #222)
2026-08-08
Rank Moved
Rank dropped 38 spots (#168 → #206)
2026-07-14
Rank Moved
Rank dropped 14 spots (#170 → #184)
2026-07-13
Rank Moved
Rank dropped 22 spots (#148 → #170)
2026-06-29
Rank Moved
Rank dropped 18 spots (#101 → #119)
2026-06-25
Scorecard Added
OSSF Scorecard: 5.1/10
2026-06-25
Grade Changed
Trust grade D → B
2026-06-25
Rank Moved
Rank rose 182 spots (#298 → #116)
2026-06-25
HVTrust Changed
HVTrust up 29.4pts (37.3 → 66.7)
2026-06-24
Rank Moved
Rank dropped 35 spots (#263 → #298)
2026-06-23
Rank Moved
Rank dropped 22 spots (#241 → #263)
2026-06-22
Rank Moved
Rank dropped 11 spots (#230 → #241)
2026-06-21
Rank Moved
Rank dropped 14 spots (#216 → #230)
2026-06-19
Rank Moved
Rank dropped 11 spots (#203 → #214)
2026-06-15
Rank Moved
Rank dropped 16 spots (#183 → #199)
2026-06-13
Rank Moved
Rank rose 13 spots (#198 → #185)
2026-06-11
Rank Moved
Rank dropped 11 spots (#186 → #197)
2026-06-02
Rank Moved
Rank dropped 14 spots (#163 → #177)
2026-06-01
Rank Moved
Rank dropped 19 spots (#144 → #163)
2026-05-29
HVTrust Changed
HVTrust up 6.7pts (26.7 → 33.4)

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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