YoMo has an HVTrust score of 45.7/100 (Grade D), ranked #200 of 300 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 45.7/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

Compare Compare saved agents Track this agent Suggest correction

Listing state

Needs review

HVTrust

45.7/100 · Grade D

Last push

2026-06-18 · 4d ago

Recent change

New

Quick Trust Read

Verdict

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

45.7/100 · Grade D

Strongest Signal

Maintenance

19.0/20

Weakest Signal

Transparency

3.1/17

What Would Improve It

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

Recent Changes

2026-06-20

Newly Listed

First tracked at rank #191

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 3.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 Track YoMo View Agent Frameworks Report missing data

77.0

Activity Score · out of 100

45.7

HVTrust Score · out of 100

#200

Global Rank · of 300

#45

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. Full methodology →

Rank Trend

2026-06-20 2026-06-21

Activity & Reach

Stars

1.9k

Forks

143

Last Push

2026-06-18

4 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #200

Analysis

HVTrust Dimensions

45.7 / 100 · 100.0% confidence

Safety / IntegrityOSSF, provenance, signatures

4.9 / 25

Identity / ProvenanceListing and build link

10.8 / 18

TransparencyLicense and public checks

3.1 / 17

MaintenanceFreshness and commits

19.0 / 20

AdoptionStars and downloads

7.9 / 20

Activity Inputs

77.0 / 100

StarsRepository reach

19.7 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

22.6 / 25

CommunityFork signal

10.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.6 / 10

OpenSSF Scorecard · scanned Jun 21, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 0

Maintained 10

Packaging -1

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 3.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 4 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

Profile context only

HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →

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.

OpenAI

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?

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

2026-06-20

Newly Listed

First tracked at rank #191

GitHub →

Embed Badge Badge guide 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 v3.2 · Raw JSON