Is Promptfoo safe?
Promptfoo scores 74.2/100 (Grade B), ranked #62 of 328 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types).
The public evidence: its packages ship with cryptographic provenance;
no OSSF Scorecard result yet;
recent commits are unsigned;
last pushed 2026-07-11. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
74.2/100 · Grade B
Strongest Signal
Identity / Provenance
18.0/18
Weakest Signal
Safety / Integrity
7.5/25
What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-06-20
Rank Moved
Rank dropped 17 spots (#49 → #66)
2026-06-20
HVTrust Changed
HVTrust down 5.0pts (76.9 → 71.9)
Maintainer Checklist
Add Scorecard coverageExpose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
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 A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed today
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
23.1k
Forks
2.1k
Last Push
2026-07-11
today
Commits (4 wk)
229
Downloads (7d)
384,010
npm
HN mentions (30d)
6
Open Issues
94
Rank Change
=
was #62
Analysis
HVTrust Dimensions
74.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
7.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.9 / 20
Activity Inputs
91.6 / 100
StarsRepository reach
26.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.4 / 20
Supply Chain Trust
Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
—
Unable to query
Is Promptfoo safe?
Promptfoo 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 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.
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.
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
high confidence
Implemented
Promptfoo appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
browser
code
shell
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
How this surface has changed
Detected changes to Promptfoo'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.
2026-06-06
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
Detected MCP server support changed: none → implemented
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 v4.2 · Raw JSON
