updated 2026-08-04 02:30 UTC

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
18.5/100
Rank #456 of 468
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 D · 1/5 signals
Last push
2026-05-29 · 67d ago
Recent change
New

Is omniclaw safe? omniclaw scores 18.5/100 (Grade D), ranked #456 of 468 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 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

#98 LLMTornado — 19.5 (D) → #99 OpenManus — 19.0 (D) → #101 harmonist — 17.3 (D) → #102 cashclaw — 13.6 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-03
Newly Listed
First tracked at rank #456
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 67 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
40.0
Activity sub-score · out of 100
#100
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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-04 02:30 UTC · Repo last pushed 67 days ago

Rank Trend

2026-08-03 2026-08-04

Activity & Reach

Stars
574
Forks
43
Last Push
2026-05-29
67 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
14
Rank Change
=
was #456

Analysis

HVTrust Dimensions vs Agent Frameworks

18.5 / 100 · 50.0% confidence

omniclaw Agent Frameworks average (103 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.1 / 25
6.9 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
8.5 / 17
3.5 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
7.5 / 20
7.1 below avg 14.6
AdoptionLog-scaled stars · package downloads
6.6 / 20
5.3 below avg 11.9

Activity Inputs

40.0 / 100
StarsRepository reach
16.6 / 30
FreshnessLast push recency
15.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
42%
of last 100 commits verified

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?
No OpenSSF Scorecard data is currently published for omniclaw. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is omniclaw actively maintained?
Slowing down. Last push was 67 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
medium confidence
1 detected
Public provider/service dependencies detected.
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

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
Listed 1
2026-08-03
Newly Listed
First tracked at rank #456
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 18.5 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON