Promptfoo

Test your prompts, agents, and RAGs. Red teaming/pentesting/vulnerability scanning for AI. Compare performance of GPT, Claude, Gemini, DeepSeek, and more. Simple declarative configs with command line and CI/CD integration. Used by OpenAI and Anthropic.

Observability & Evaluation TypeScript Listed MIT

Is Promptfoo safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.6 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare Promptfoo

How does it stack up against its Observability & Evaluation neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Promptfoo scores 92.6/100 (Grade A), ranked #7 of 1371 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; OSSF Scorecard rates its supply-chain practices 7.6/10; 100% of recent commits are signed; no published advisory affects its latest release (promptfoo); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Promptfoo 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 Promptfoo 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 Signed

    github.com/promptfoo/promptfoo, MIT, last pushed 2026-10-09. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 7.6/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:

    • Code Review8
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 8
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 6
    SAST 7
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 0
  3. Published packages Linked and attested

    • npm promptfoo Source link points back to this repo Build provenance attested
  4. What you install today No known advisories

    Latest release checked: promptfoo 0.124.1. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

  • 2026-08-11 OSSF Scorecard: 7.6/10

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Promptfoo’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 Promptfoo compares in Observability & Evaluation

  1. #1 Promptfoo 92.6 this agent
  2. #2 MLflow 89.6 −3.0
  3. #3 OpenLLMetry 86.1 −6.5
  4. #4 Weights & Biases Weave 84.3 −8.3
  5. #5 LangWatch 83.1 −9.5

Bars show each HVTrust score; the tick marks Promptfoo’s 92.6.

Where the 92.6 comes from

HVTrust dimensions vs the Observability & Evaluation average

92.6 / 100 · 100.0% confidence

Promptfoo Observability & Evaluation average (26 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
22.0 / 25
10.8 above avg 11.2
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
15.0 / 17
3.0 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
4.7 above avg 15.3
AdoptionLog-scaled stars · package downloads
18.5 / 20
5.1 above avg 13.4

Quick Trust Read

What Would Improve It
Improve safety / integrity to lift the weakest part of the trust profile.
Recent Changes
2026-09-19
Provider Added
Runtime surface grew — new detected provider dependency: Amazon Bedrock
Maintainer Checklist
Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.
92.3
Activity sub-score · out of 100
#1

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 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 refreshed 2026-10-09 12:08 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
25.8k
Forks
2.5k
Last Push
2026-10-09
today
Commits (4 wk)
516
Downloads (7d)
850,078
npm
HN mentions (30d)
6
Open Issues
126
Rank Change
▲1
was #8

Analysis

Activity Inputs

92.3 / 100
StarsRepository reach
26.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.8 / 20

Common questions about Promptfoo

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?
Promptfoo has an OpenSSF Scorecard score of 7.6/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 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.

Compare Promptfoo 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
high confidence
Implemented
Promptfoo appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 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.
  • browser
  • code
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-09-19
Provider Added
Runtime surface grew — new detected provider dependency: Amazon Bedrock

Maintain Promptfoo?

For maintainers

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.

Reputation Timeline

Signal history
Scorecard 1HVTrust 1Rank 1Surface 1
2026-09-19
Provider Added
Runtime surface grew — new detected provider dependency: Amazon Bedrock
2026-09-03
Rank Moved
Rank rose 18 spots (#21 → #3)
2026-09-03
HVTrust Changed
HVTrust up 3.7pts (88.6 → 92.3)
2026-08-11
Scorecard Added
OSSF Scorecard: 7.6/10

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 92.6 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/promptfoo.svg)](https://hvtracker.net/agents/promptfoo)
HTML:
<a href="https://hvtracker.net/agents/promptfoo"><img src="https://hvtracker.net/badge/promptfoo.svg" alt="HVTrust"></a>

Other agents in Observability & Evaluation

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON