updated 2026-06-24 17:30 UTC

Pi

earendil-works/pi

AI agent toolkit: unified LLM API, agent loop, TUI, coding agent CLI

Coding Agents TypeScript Grade C Listed MIT
Compare Compare saved agents Track this agent Suggest correction
Listing state
Listed
HVTrust
60.4/100 · Grade C
Last push
2026-06-24 · 0d ago
Recent change
New

Quick Trust Read

Verdict
Promising trust profile, but some evidence still deserves review.
60.4/100 · Grade C
Strongest Signal
Maintenance
20.0/20
Weakest Signal
Safety / Integrity
5.8/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-06-24
Newly Listed
First tracked at rank #173
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.3/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 Track Pi View Coding Agents Report missing data
97.0
Activity Score · out of 100
60.4
HVTrust Score · out of 100
#173
Global Rank · of 317
#20
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. Full methodology →

Signals refreshed 2026-06-24 17:30 UTC · Repo last pushed today

Activity & Reach

Stars
65.3k
Forks
8.0k
Last Push
2026-06-24
today
Commits (4 wk)
439
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
39
Rank Change
NEW

Analysis

HVTrust Dimensions

60.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.8 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.2 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
11.6 / 20

Activity Inputs

97.0 / 100
StarsRepository reach
28.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
18.1 / 20

Supply Chain Trust

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

Is Pi safe?

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 Pi publish package provenance?
No published build provenance is currently detected for Pi. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Pi have an OpenSSF Scorecard?
Pi has an OpenSSF Scorecard score of 4.3/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 Pi actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Pi use?
Pi ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Pi's commits signed?
8% of the last 100 commits to 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

Profile context only

HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
  • Amazon Bedrock
  • Anthropic
  • Google Gemini
  • OpenAI
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
  • code
  • filesystem
  • shell
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 Pi?

HVTrust scores 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.

Submit a correction → Add the trust badge

Reputation Timeline

Listed 1
2026-06-24
Newly Listed
First tracked at rank #173
GitHub →

Embed Badge Badge guide for maintainers →

HVTrust 60.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/pi.svg)](https://hvtracker.net/agents/pi)
HTML:
<a href="https://hvtracker.net/agents/pi"><img src="https://hvtracker.net/badge/pi.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 v3.2 · Raw JSON