updated 2026-08-06 03:30 UTC

YoMo

yomorun/yomo

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

Agent Frameworks Rust Grade D Needs review Unlicensed
45.3/100
Rank #347 of 468
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-08-05 · 1d ago
Recent change
No recent signal change

Is YoMo safe? YoMo scores 45.3/100 (Grade D), ranked #347 of 468 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.6/10; 9% of recent commits are signed; last pushed 2026-08-05. Every point is earned from checkable signals — never paid placement. How scoring works →

Active listing, but review is needed
  • [4.1.1] no declared license (GitHub license field is null)

Ranked neighbours in Agent Frameworks

#72 Fedml — 46.0 (D) → #73 Parlant — 45.6 (D) → #75 Mastra — 45.3 (D) → #76 Upsonic — 44.9 (D) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
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.6/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
70.1
Activity sub-score · out of 100
#74
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 →

Signals refreshed 2026-08-06 03:30 UTC · Repo last pushed yesterday

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
1.9k
Forks
144
Last Push
2026-08-05
yesterday
Commits (4 wk)
16
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #347

Analysis

HVTrust Dimensions vs Agent Frameworks

45.3 / 100 · 100.0% confidence

YoMo Agent Frameworks average (103 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.2 / 25
2.8 below avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
3.9 / 17
8.1 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
16.8 / 20
2.2 above avg 14.6
AdoptionLog-scaled stars · package downloads
7.9 / 20
4.0 below avg 11.9

Activity Inputs

70.1 / 100
StarsRepository reach
19.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
15.3 / 25
CommunityFork signal
10.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Aug 5, 2026
Signed Commits
9%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 6
CI-Tests 8
CII-Best-Practices 0
Code-Review 7
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.6/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?
9% 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
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • code
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
Rank 6Listed 1
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)
2026-06-20
Newly Listed
First tracked at rank #191
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 45.3 Grade D
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.2 · Raw JSON