Is omniclaw safe to use?

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

What is the trust score for omniclaw?

omniclaw scores 42.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 579 GitHub stars and is categorized under Agent Frameworks.

omniclaw

omnuron/omniclaw

The first agentic payment network: policy-controlled, gasless, and real money-ready. OmniClaw CLI + Financial Policy En

Agent Frameworks Python Grade D Listed MIT

42.6/100

Rank #1108 of 1328

Compare omniclaw

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

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-05-29 · 112d ago

Recent change

Rank

Is omniclaw safe? omniclaw scores 42.6/100 (Grade D), ranked #1108 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.5/10; 42% of recent commits are signed; last pushed 2026-05-29. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#97 YoMo — 44.4 (D) → #98 PocketFlow — 43.8 (D) → #100 LLMTornado — 41.6 (D) → #101 Upsonic — 41.3 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-12

Rank Moved

Rank dropped 12 spots (#1092 → #1104)

2026-09-09

Rank Moved

Rank dropped 18 spots (#1071 → #1089)

2026-09-07

Rank Moved

Rank dropped 32 spots (#1030 → #1062)

Maintainer Checklist

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

Refresh maintenance signals The repo was last pushed 112 days ago. Fresh activity helps separate stable projects from stale ones.

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

33.6

Activity sub-score · out of 100

#99

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-18

Activity & Reach

Stars

579

Forks

Last Push

2026-05-29

112 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #1110

Analysis

HVTrust Dimensions vs Agent Frameworks

42.6 / 100 · 100.0% confidence

omniclaw Agent Frameworks average (122 agents)

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

7.7 / 25

2.0 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

12.3 / 17

in line with avg 12.4

Maintenance60% last-push freshness · 40% commit activity

4.5 / 20

9.4 below avg 13.9

AdoptionLog-scaled stars · package downloads

6.6 / 20

4.6 below avg 11.2

Activity Inputs

33.6 / 100

StarsRepository reach

16.6 / 30

FreshnessLast push recency

9.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

7.6 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.5 / 10

OpenSSF Scorecard · scanned Sep 16, 2026

Signed Commits

42%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is omniclaw safe?

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

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

Does omniclaw have an OpenSSF Scorecard?

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

Slowing down. Last push was 112 days ago — keep an eye on whether activity resumes.

What license does omniclaw use?

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

Are omniclaw's commits signed?

42% of the last 100 commits to omniclaw 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

high confidence

Implemented

omniclaw appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Redis

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

database

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

How this surface has changed

Detected changes to omniclaw'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-08-27

Activity Went Stale

No commits for 90 days

Maintain omniclaw?

For maintainers

HVTrust scores omniclaw 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-12

Rank Moved

Rank dropped 12 spots (#1092 → #1104)

2026-09-09

Rank Moved

Rank dropped 18 spots (#1071 → #1089)

2026-09-07

Rank Moved

Rank dropped 32 spots (#1030 → #1062)

2026-09-06

Rank Moved

Rank dropped 16 spots (#1014 → #1030)

2026-09-05

Rank Moved

Rank dropped 46 spots (#968 → #1014)

2026-09-04

Rank Moved

Rank dropped 26 spots (#942 → #968)

2026-09-03

Rank Moved

Rank dropped 59 spots (#883 → #942)

2026-09-02

Rank Moved

Rank dropped 47 spots (#836 → #883)

2026-09-01

Rank Moved

Rank dropped 29 spots (#807 → #836)

2026-08-31

Scorecard Added

OSSF Scorecard: 4.5/10

2026-08-31

Rank Moved

Rank rose 459 spots (#1266 → #807)

2026-08-31

HVTrust Changed

HVTrust up 26.2pts (17.6 → 43.8)

2026-08-30

Rank Moved

Rank dropped 11 spots (#1255 → #1266)

2026-08-29

Rank Moved

Rank dropped 14 spots (#1241 → #1255)

2026-08-28

Rank Moved

Rank dropped 13 spots (#1228 → #1241)

2026-08-27

Activity Went Stale

No commits for 90 days

2026-08-27

Rank Moved

Rank dropped 12 spots (#1216 → #1228)

2026-08-26

Rank Moved

Rank dropped 38 spots (#1178 → #1216)

2026-08-16

Rank Moved

Rank dropped 31 spots (#1150 → #1181)

2026-08-10

Rank Moved

Rank dropped 67 spots (#1078 → #1145)

2026-08-08

Rank Moved

Rank dropped 575 spots (#502 → #1077)

2026-08-06

Rank Moved

Rank dropped 32 spots (#456 → #488)

2026-08-03

Newly Listed

First tracked at rank #456

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/omniclaw.svg)](https://hvtracker.net/agents/omniclaw)
            
HTML:
            <a href="https://hvtracker.net/agents/omniclaw"><img src="https://hvtracker.net/badge/omniclaw.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