oh-my-pi
⌥ AI Coding agent for the terminal — hash-anchored edits, optimized tool harness, LSP, Python, browser, subagents, and
Compare oh-my-pi
How does it stack up against its Coding Agents neighbours?
Pick any agent to compare →Strong public trust posture, backed by multiple independent signals.
Is oh-my-pi safe? oh-my-pi scores 85.6/100 (Grade A), ranked #46 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.8/10; 95% of recent commits are signed; last pushed 2026-08-22. Every point is earned from checkable signals — never paid placement. How scoring works →
Ranked neighbours in Coding Agents
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
HVTrust Dimensions vs Coding Agents
85.6 / 100 · 100.0% confidenceoh-my-pi Coding Agents average (70 agents)
Activity Inputs
92.4 / 100Supply Chain Trust
Is oh-my-pi safe?
Does oh-my-pi publish package provenance?
Does oh-my-pi have an OpenSSF Scorecard?
Is oh-my-pi actively maintained?
What license does oh-my-pi use?
Are oh-my-pi's commits signed?
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.
Compare oh-my-pi head-to-head
AI agent surface
MCP, providers, tool surface
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to oh-my-pi'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.
Maintain oh-my-pi?
For maintainers
HVTrust scores oh-my-pi 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/oh-my-pi)
<a href="https://hvtracker.net/agents/oh-my-pi"><img src="https://hvtracker.net/badge/oh-my-pi.svg" alt="HVTrust"></a>
Other agents in Coding Agents
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON