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. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed today
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
21.9k
Forks
1.9k
Last Push
2026-06-04
today
Commits (4 wk)
409
Downloads (7d)
277,927
npm
HN mentions (30d)
3
Open Issues
311
Rank Change
▼2
was #35
Analysis
HVTrust Dimensions
76.7 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.5 / 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
17.7 / 20
Activity Inputs
91.3 / 100
StarsRepository reach
26.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.3 / 20
Supply Chain Trust
Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
100%
of last 100 commits verified
Is Promptfoo safe?
Public supply-chain signals for Promptfoo are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Promptfoo carries less obvious unverified-evidence risk than projects with thin signals.
Does Promptfoo publish package provenance?
Yes. Promptfoo's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Promptfoo have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Promptfoo. 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 Promptfoo actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Promptfoo use?
Promptfoo ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Promptfoo's commits signed?
100% of the last 100 commits to Promptfoo 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Promptfoo?
HVTrust scores Promptfoo 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) · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
