updated 2026-08-11 21:02 UTC

oh-my-openagent

code-yeongyu/oh-my-openagent

omo/lazycodex: The coding agent for tokenmaxxers;the one and only agent harness for complex codebases. For your Codex, f

Coding Agents TypeScript Grade C Listed NOASSERTION Source-available
63.3/100
Rank #269 of 1283
Compare oh-my-openagent

How does it stack up against its Coding Agents neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-11 · 0d ago
Recent change
Rank +2

Is oh-my-openagent safe? oh-my-openagent scores 63.3/100 (Grade C), ranked #269 of 1283 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; 21% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

#20 SWE-agent — 64.2 (C) → #21 Claude Code — 64.0 (C) → #23 Potpie — 62.4 (C) → #24 Archon — 62.0 (C) →

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 16 spots (#251 → #267)
2026-08-08
Rank Moved
Rank dropped 62 spots (#174 → #236)
2026-08-07
Scorecard Added
OSSF Scorecard: 5.3/10
Maintainer Checklist
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.
Compare with another agent Get email alerts for oh-my-openagent View Coding Agents Report missing data
96.4
Activity sub-score · out of 100
#22
In Coding Agents

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-11 21:02 UTC · Repo last pushed today

Activity & Reach

Stars
67.7k
Forks
5.5k
Last Push
2026-08-11
today
Commits (4 wk)
1748
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
427
Rank Change
▼2
was #267

Analysis

HVTrust Dimensions vs Coding Agents

63.3 / 100 · 100.0% confidence

oh-my-openagent Coding Agents average (67 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.8 / 25
0.9 below avg 7.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
1.3 above avg 11.1
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.7 above avg 15.3
AdoptionLog-scaled stars · package downloads
11.6 / 20
0.6 below avg 12.2

Activity Inputs

96.4 / 100
StarsRepository reach
29.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.4 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Aug 11, 2026
Signed Commits
21%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 9
Maintained 10
Packaging 10
Pinned-Dependencies 1
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is oh-my-openagent safe?

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. oh-my-openagent may have internal security practices not visible through public signals.
oh-my-openagent has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does oh-my-openagent publish package provenance?
No published build provenance is currently detected for oh-my-openagent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does oh-my-openagent have an OpenSSF Scorecard?
oh-my-openagent 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 oh-my-openagent actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does oh-my-openagent use?
oh-my-openagent ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are oh-my-openagent's commits signed?
21% of the last 100 commits to oh-my-openagent 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
oh-my-openagent 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.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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 oh-my-openagent?

For maintainers

HVTrust scores oh-my-openagent 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 5Listed 1Scorecard 1
2026-08-10
Rank Moved
Rank dropped 16 spots (#251 → #267)
2026-08-08
Rank Moved
Rank dropped 62 spots (#174 → #236)
2026-08-07
Scorecard Added
OSSF Scorecard: 5.3/10
2026-07-29
Rank Moved
Rank dropped 11 spots (#410 → #421)
2026-07-15
Rank Moved
Rank dropped 21 spots (#381 → #402)
2026-07-14
Rank Moved
Rank dropped 25 spots (#356 → #381)
2026-07-13
Newly Listed
First tracked at rank #356
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/oh-my-openagent.svg)](https://hvtracker.net/agents/oh-my-openagent)
HTML:
<a href="https://hvtracker.net/agents/oh-my-openagent"><img src="https://hvtracker.net/badge/oh-my-openagent.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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