Promptfoo
snapshot-20260907 commercialThe section your link pointed to isn't on Promptfoo's page any more, so we've brought you to the top.
Promptfoo tests, evaluates, and red-teams LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. applications to detect vulnerabilities and compare model outputs.
promptfoo logs
promptfoo redteam generate -d "prod-telecom-scan-2026-08"
promptfoo eval --env-file .env.shared --env-file .env.staging
# promptfooconfig.yaml snippet
redteam:
strategies:
- id: jailbreak
numTests: 20
prompts:
- file://$PROMPTS_DIR/system.txt
promptfoo logs
promptfoo eval --env-file .env.base --env-file .env.staging
promptfoo logs
promptfoo eval --env-file .env.base --env-file .env.prod
promptfoo logs
promptfoo redteam generate -d "Telecom voice agent test" --plugins telecom --config redteam.yaml
promptfoo eval --env-file .env.base --env-file .env.staging
promptfoo logs
promptfoo logs
promptfoo logs
promptfoo eval --env-file .env.shared --env-file .env.staging
promptfoo redteam generate -d "Sprint 42 telecom compliance scan"
promptfoo eval --env-file .env.shared --env-file .env.local
promptfoo logs
promptfoo redteam generate -d "Telecom Q1 regression scan"
promptfoo eval --env-file .env.base --env-file .env.staging --prompts prompts.yaml --tests tests.yaml
promptfoo redteam generate -d 'telecom-smoke-test' --config redteam.yaml
promptfoo redteam generate -d 'PR #482 telecom safety check' --numTests 10
promptfoo eval --env-file .env.shared --env-file .env.local
promptfoo logs
promptfoo redteam scan --env-file .env.prod --env-file .env.secrets
promptfoo redteam generate -d "Q3 telecom safety audit" --plugins telecom
promptfoo logs
promptfoo eval --env-file .env.local --env-file .env.prod
promptfoo redteam generate --numTests 10 --description 'Basic safety check'
PROMPTFOO_MAX_EVAL_TIME_MS=30000 promptfoo eval
Summary
Promptfoo is a commercial ai-security tool that tests and red-teams LLM applications, run from the command line in CI pipelines or locally by developers. It covers both evaluation, letting teams score model or prompt outputs against assertions like word-count checks or derived metrics, and adversarial testing, generating attacks through plugins such as its Telecom-specific suite or RAGRAGRetrieval-augmented generation: looking up relevant documents and adding them to the prompt before the model answers. It grounds responses in private or current data without retraining. Source Attribution checks, with scans configurable at the individual test-case level for prompts, providers, and structured outputstructured outputForcing a model's response to match a given format or JSON schema, so software can parse it reliably instead of hoping the text is well formed.. It's aimed at application developers and AI security teams building on models from providers like AWS Bedrock, Azure AI Foundry, xAI, or Hugging Face via Transformers.js, all of which it can connect to directly. Launched in 2023 and still active, with 17 releases in the tracked window and the latest just 34 days old.
Promptfoo tests, evaluates, and red-teams LLM applications to detect vulnerabilities and compare model outputs.
How Promptfoo helps
Which prompts would let an attacker extract data or bypass safety rules before this ships to production?
runs adversarial plugins that generate attacks like jailbreaks and data-extraction attempts against the application and reports which ones succeeded, at the individual test-case level
Is my RAG system citing sources it shouldn't be trusting, or failing to cite ones it should?
runs the Source Attribution checks against retrieved documents and flags responses that misattribute or drop the source
Does my telecom AI system leak information specific to that industry's attack surface?
runs the telecom-specific plugin suite, generating attacks tailored to telecom scenarios and reporting which prompts got through
Did switching models or rewriting a prompt make the output worse?
scores each provider or prompt's output against the same assertions, including word-count checks and derived metrics like averages, and lines up the results side by side
Which of my test cases are actually exercising the provider or structured-output config I think they are?
lets prompts, providers, and structured output be set per test case, and shows the provider configuration used for each result inline
Why did my last scan fail partway through or behave unexpectedly against my provider?
writes log output that can be viewed directly to see where a provider call or scan step broke down
Languages
Command line
20 commands for Promptfoo, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.
No command matches.
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Promptfoo, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Promptfoo puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Commercials
pricing & packaging history · Promptfoo vendor page19 readings of Promptfoo's pricing page since Sep 2024, with 1 relaunch of its plan lineup and 2 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
promptfoo.dev, every changePromptfoo's home page and 15 more pages as they looked each month from May 2023 to October 2026: 24 renders, 5 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
21 entries
No entries match these filters.
- September 20261
- August 20263
- July 20269
- January 20261
- December 20251
- November 20251
- October 20251
- September 20251
- August 20251
- July 20251
- June 20251
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.