oh-my-pi

⌥ Coding agent with the IDE wired in. Built by Stencil Labs.

Coding Agents TypeScript Listed MIT

Is oh-my-pi safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 4.7 / 10
Provenance Attested
Signed commits 30%
Last push today
Advisories None known
Compare oh-my-pi
Suggest a correction

In detail: oh-my-pi scores 83.7/100 (Grade A), ranked #123 of 1387 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.7/10; 30% of recent commits are signed; no published advisory affects its latest release (@oh-my-pi/pi-coding-agent); last pushed 2026-11-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How oh-my-pi could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships oh-my-pi and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/can1357/oh-my-pi, MIT, last pushed 2026-11-22. 30% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.7/10 (scanned Nov 7, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review4
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 4
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 0
  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @oh-my-pi/pi-coding-agent 19.0.1. No published advisory affects it (OSV, checked 2026-11-21).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of oh-my-pi.

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues oh-my-pi’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How oh-my-pi compares in Coding Agents

  1. #4 Bernstein 87.8 +4.1
  2. #5 Qwen Code 87.4 +3.7
  3. #6 oh-my-pi 83.7 this agent
  4. #7 Mistral Vibe 83.1 −0.6
  5. #8 Hermes Agent 82.6 −1.1

Bars show each HVTrust score; the tick marks oh-my-pi’s 83.7.

Where the 83.7 comes from

HVTrust dimensions vs the Coding Agents average

83.7 / 100 · 100.0% confidence

oh-my-pi Coding Agents average (77 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.9 / 25
5.7 above avg 9.2
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
6.3 above avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
12.5 / 17
0.5 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.7 above avg 14.3
AdoptionLog-scaled stars · package downloads
18.3 / 20
6.2 above avg 12.1

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-20
Rank Moved
Rank dropped 21 spots (#103 → #124)
2026-11-18
Rank Moved
Rank rose 37 spots (#141 → #104)
2026-11-17
Rank Moved
Rank dropped 38 spots (#103 → #141)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.7/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
94.6
Activity sub-score · out of 100
#6

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 →

Signals refreshed 2026-11-22 12:09 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-22

Activity & Reach

Stars
39.6k
Forks
4.6k
Last Push
2026-11-22
today
Commits (4 wk)
7432
Downloads (7d)
306,076
npm
HN mentions (30d)
—
Open Issues
3003
Rank Change
=
was #123

Analysis

Activity Inputs

94.6 / 100
StarsRepository reach
27.6 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.0 / 20

Common questions about oh-my-pi

Public supply-chain signals for oh-my-pi are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but oh-my-pi carries less obvious unverified-evidence risk than projects with thin signals.
Does oh-my-pi publish package provenance?
Yes. oh-my-pi's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does oh-my-pi have an OpenSSF Scorecard?
oh-my-pi has an OpenSSF Scorecard score of 4.7/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-pi actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does oh-my-pi use?
oh-my-pi ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are oh-my-pi's commits signed?
30% of the last 100 commits to oh-my-pi 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.

Compare oh-my-pi head-to-head

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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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-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
Rank 28HVTrust 5Grade 4
2026-11-20
Rank Moved
Rank dropped 21 spots (#103 → #124)
2026-11-18
Rank Moved
Rank rose 37 spots (#141 → #104)
2026-11-17
Rank Moved
Rank dropped 38 spots (#103 → #141)
2026-11-16
Rank Moved
Rank rose 23 spots (#126 → #103)
2026-11-11
Rank Moved
Rank dropped 24 spots (#111 → #135)
2026-11-09
Rank Moved
Rank dropped 29 spots (#82 → #111)
2026-11-08
Rank Moved
Rank rose 17 spots (#99 → #82)
2026-11-06
Rank Moved
Rank rose 33 spots (#126 → #93)
2026-10-31
Rank Moved
Rank dropped 18 spots (#98 → #116)
2026-10-29
Rank Moved
Rank rose 17 spots (#114 → #97)
2026-10-24
Rank Moved
Rank rose 13 spots (#123 → #110)
2026-10-22
Rank Moved
Rank dropped 19 spots (#105 → #124)
2026-10-04
Rank Moved
Rank dropped 26 spots (#76 → #102)
2026-10-02
Rank Moved
Rank rose 31 spots (#107 → #76)
2026-09-30
Rank Moved
Rank dropped 44 spots (#62 → #106)
2026-09-30
HVTrust Changed
HVTrust down 3.2pts (86.5 → 83.3)
2026-09-28
Rank Moved
Rank rose 24 spots (#85 → #61)
2026-09-25
Rank Moved
Rank rose 12 spots (#99 → #87)
2026-09-23
Rank Moved
Rank dropped 35 spots (#56 → #91)
2026-09-21
Rank Moved
Rank rose 26 spots (#82 → #56)
2026-09-13
Rank Moved
Rank rose 11 spots (#95 → #84)
2026-09-06
Rank Moved
Rank dropped 10 spots (#81 → #91)
2026-09-05
Grade Changed
Trust grade C → A
2026-09-05
Rank Moved
Rank rose 642 spots (#723 → #81)
2026-09-05
HVTrust Changed
HVTrust up 31.7pts (52.1 → 83.8)
2026-09-04
Rank Moved
Rank dropped 50 spots (#673 → #723)
2026-09-03
Rank Moved
Rank dropped 35 spots (#638 → #673)
2026-09-02
Grade Changed
Trust grade A → C
2026-09-02
Rank Moved
Rank dropped 574 spots (#64 → #638)
2026-09-02
HVTrust Changed
HVTrust down 32.0pts (84.8 → 52.8)
2026-08-31
Grade Changed
Trust grade C → A
2026-08-31
Rank Moved
Rank rose 504 spots (#568 → #64)
2026-08-31
HVTrust Changed
HVTrust up 32.0pts (52.5 → 84.5)
2026-08-30
Grade Changed
Trust grade A → C
2026-08-30
Rank Moved
Rank dropped 508 spots (#60 → #568)
2026-08-30
HVTrust Changed
HVTrust down 32.1pts (84.6 → 52.5)
2026-08-27
Rank Moved
Rank dropped 11 spots (#55 → #66)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 83.7 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/oh-my-pi.svg)](https://hvtracker.net/agents/oh-my-pi)
HTML:
<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

Data sources
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.4 · Raw JSON