YoMo has an HVTrust score of 47.4/100 (Grade D), ranked #998 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for YoMo?

YoMo scores 47.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.9k GitHub stars and is categorized under Agent Frameworks.

YoMo

yomorun/yomo

🦖 Serverless AI Agent Framework with Geo-distributed Edge AI Infra.

Agent Frameworks Rust Grade D Needs review Unlicensed

47.4/100

Rank #998 of 1328

Compare YoMo

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Needs review

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-20 · 0d ago

Recent change

Rank +1

Is YoMo safe? YoMo scores 47.4/100 (Grade D), ranked #998 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 4.9/10; 44% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#86 OpenEvolve — 48.0 (D) → #87 OpenRath — 47.4 (D) → #89 Fedml — 47.1 (D) → #90 OpenFang — 46.8 (D) →

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 rose 25 spots (#1023 → #998)

2026-09-19

Rank Moved

Rank rose 41 spots (#1064 → #1023)

2026-09-12

Rank Moved

Rank dropped 61 spots (#999 → #1060)

Maintainer Checklist

Declare an open license Publish a clear OSI-approved license so usage and maintenance terms are independently verifiable.

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

Review Flags

[4.1.1] no declared license (GitHub license field is null)

Compare with another agent Get email alerts for YoMo View Agent Frameworks Report missing data

67.8

Activity sub-score · out of 100

#88

In Agent Frameworks

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-09-20

Activity & Reach

Stars

1.9k

Forks

147

Last Push

2026-09-20

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲25

was #1023

Analysis

HVTrust Dimensions vs Agent Frameworks

47.4 / 100 · 100.0% confidence

YoMo Agent Frameworks average (122 agents)

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

8.3 / 25

1.4 below avg 9.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

4.2 / 17

8.2 below avg 12.4

Maintenance60% last-push freshness · 40% commit activity

16.2 / 20

2.3 above avg 13.9

AdoptionLog-scaled stars · package downloads

7.9 / 20

3.3 below avg 11.2

Activity Inputs

67.8 / 100

StarsRepository reach

19.7 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

13.0 / 25

CommunityFork signal

10.1 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.9 / 10

OpenSSF Scorecard · scanned Sep 17, 2026

Signed Commits

44%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 0

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 9

Is YoMo safe?

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

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

Does YoMo have an OpenSSF Scorecard?

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

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

What license does YoMo use?

YoMo ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are YoMo's commits signed?

44% of the last 100 commits to YoMo 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

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

None detected

No clear plugin system or broad tool 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 YoMo?

For maintainers

HVTrust scores YoMo 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-09-20

Rank Moved

Rank rose 25 spots (#1023 → #998)

2026-09-19

Rank Moved

Rank rose 41 spots (#1064 → #1023)

2026-09-12

Rank Moved

Rank dropped 61 spots (#999 → #1060)

2026-09-11

Rank Moved

Rank dropped 21 spots (#978 → #999)

2026-09-10

Rank Moved

Rank rose 24 spots (#1002 → #978)

2026-09-09

Rank Moved

Rank rose 33 spots (#1035 → #1002)

2026-09-08

Rank Moved

Rank dropped 11 spots (#1024 → #1035)

2026-09-07

Rank Moved

Rank dropped 82 spots (#942 → #1024)

2026-09-06

Rank Moved

Rank dropped 19 spots (#923 → #942)

2026-09-05

Rank Moved

Rank dropped 57 spots (#866 → #923)

2026-09-04

Rank Moved

Rank dropped 36 spots (#830 → #866)

2026-09-02

Rank Moved

Rank dropped 44 spots (#782 → #826)

2026-09-01

Rank Moved

Rank dropped 33 spots (#749 → #782)

2026-08-31

Rank Moved

Rank dropped 22 spots (#727 → #749)

2026-08-30

Rank Moved

Rank dropped 23 spots (#704 → #727)

2026-08-29

Rank Moved

Rank dropped 48 spots (#656 → #704)

2026-08-28

Rank Moved

Rank dropped 16 spots (#640 → #656)

2026-08-27

Rank Moved

Rank dropped 21 spots (#619 → #640)

2026-08-26

Rank Moved

Rank dropped 94 spots (#525 → #619)

2026-08-19

Rank Moved

Rank dropped 11 spots (#519 → #530)

2026-08-17

Rank Moved

Rank rose 10 spots (#536 → #526)

2026-08-15

Rank Moved

Rank dropped 12 spots (#516 → #528)

2026-08-13

Rank Moved

Rank dropped 15 spots (#502 → #517)

2026-08-12

Rank Moved

Rank rose 17 spots (#519 → #502)

2026-08-10

Rank Moved

Rank dropped 16 spots (#504 → #520)

2026-08-08

Rank Moved

Rank dropped 133 spots (#363 → #496)

2026-07-29

Rank Moved

Rank dropped 14 spots (#338 → #352)

2026-07-15

Rank Moved

Rank dropped 20 spots (#307 → #327)

2026-07-14

Rank Moved

Rank dropped 16 spots (#291 → #307)

2026-07-13

Rank Moved

Rank dropped 35 spots (#256 → #291)

2026-06-24

Rank Moved

Rank dropped 25 spots (#223 → #248)

2026-06-23

Rank Moved

Rank dropped 14 spots (#209 → #223)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

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