Neo has an HVTrust score of 88.1/100 (Grade A), ranked #23 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Neo?

Neo scores 88.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.3k GitHub stars and is categorized under UI & App Builders.

Neo

neomjs/neo

Neo.mjs is a self-evolving software organism: a professional end-to-end AI engineering team whose cross-model swarm inha

UI & App Builders JavaScript Grade A Listed MIT

88.1/100

Rank #23 of 1283

Compare Neo

How does it stack up against its UI & App Builders neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-11 · 0d ago

Recent change

No recent signal change

Is Neo safe? Neo scores 88.1/100 (Grade A), ranked #23 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.8/10; 78% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

#2 OpenUI — 86.8 (A) → #3 Tambo — 83.6 (A) → #4 Open WebUI — 83.4 (A) → #5 LibreChat — 74.2 (B) →

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.8/10. Tighten the weakest checks to improve public safety evidence.

Compare with OpenUI Get email alerts for Neo View UI & App Builders Report missing data

82.1

Activity sub-score · out of 100

In UI & App Builders

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A 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 →

Activity & Reach

Stars

3.3k

Forks

230

Last Push

2026-08-11

today

Commits (4 wk)

1048

Downloads (7d)

4,945

npm

HN mentions (30d)

—

Open Issues

317

Rank Change

was #23

Analysis

HVTrust Dimensions vs UI & App Builders

88.1 / 100 · 100.0% confidence

Neo UI & App Builders average (17 agents)

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

18.6 / 25

8.5 above avg 10.1

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

5.5 above avg 12.5

Transparency50% declared license · 50% OSSF Scorecard

13.4 / 17

1.5 above avg 11.9

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

3.9 above avg 16.1

AdoptionLog-scaled stars · package downloads

13.4 / 20

1.0 above avg 12.4

Activity Inputs

82.1 / 100

StarsRepository reach

21.1 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

11.0 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.8 / 10

OpenSSF Scorecard · scanned Aug 11, 2026

Signed Commits

78%

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 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 1

SAST 10

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 4

Is Neo safe?

Public supply-chain signals for Neo are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Neo carries less obvious unverified-evidence risk than projects with thin signals.

Does Neo publish package provenance?

Yes. Neo's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Neo have an OpenSSF Scorecard?

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

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

What license does Neo use?

Neo ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Neo's commits signed?

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

Neo vs OpenUI → Neo vs Tambo → Neo vs Open WebUI →

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

high confidence

Implemented

Neo appears to expose MCP server capabilities.

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

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

How this surface has changed

Detected changes to Neo'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-06-16

Provenance Added

Package provenance attestation detected

2026-06-15

Provenance Removed

Package provenance attestation no longer detected

2026-06-13

Provenance Added

Package provenance attestation detected

2026-06-01

Activity Resumed

Activity resumed

Maintain Neo?

For maintainers

HVTrust scores Neo 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-06-16

Provenance Added

Package provenance attestation detected

2026-06-16

Grade Changed

Trust grade B → A

2026-06-16

Rank Moved

Rank rose 58 spots (#91 → #33)

2026-06-16

HVTrust Changed

HVTrust up 15.8pts (66.5 → 82.3)

2026-06-15

Provenance Removed

Package provenance attestation no longer detected

2026-06-15

Grade Changed

Trust grade A → B

2026-06-15

Rank Moved

Rank dropped 58 spots (#33 → #91)

2026-06-15

HVTrust Changed

HVTrust down 16.4pts (82.9 → 66.5)

2026-06-13

Provenance Added

Package provenance attestation detected

2026-06-13

Grade Changed

Trust grade B → A

2026-06-13

Rank Moved

Rank rose 57 spots (#91 → #34)

2026-06-13

HVTrust Changed

HVTrust up 16.1pts (66.7 → 82.8)

2026-06-01

Scorecard Added

OSSF Scorecard: 5.4/10

2026-06-01

Activity Resumed

Activity resumed

2026-06-01

Grade Changed

Trust grade D → C

2026-06-01

Rank Moved

Rank rose 92 spots (#182 → #90)

2026-06-01

HVTrust Changed

HVTrust up 62.7pts (0.0 → 62.7)

2026-06-01

Activity Score Changed

Activity score up 82pts (0 → 82)

2026-05-31

Newly Listed

First tracked at rank #182

GitHub → npm: neo.mjs

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in UI & App Builders

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