How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 refreshed2026-07-07 22:30 UTC·Repo last pushed today
Activity & Reach
Stars
16.6k
Forks
1.5k
Last Push
2026-07-07
today
Commits (4 wk)
4914
Downloads (7d)
63,463
npm
HN mentions (30d)
—
Open Issues
429
Rank Change
NEW
Analysis
HVTrust Dimensions
73.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.7 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
16.5 / 20
Activity Inputs
90.0 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
14.7 / 20
Supply Chain Trust
Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
64%
of last 100 commits verified
Is oh-my-pi safe?
oh-my-pi 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-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?
No OpenSSF Scorecard data is currently published for oh-my-pi. 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 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?
64% 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.
AI agent 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 →
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
4 detected
Public provider/service dependencies detected.
Anthropic
Firecrawl
OpenAI
Tavily
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Marketplace
Marketplace plugin/integration surface detected.
browser
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?
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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON
