Comparison
vigil-llm vs promptfoo
Verdict
Pick vigil-llm if vigil-llm is designed for users who need robust security measures to protect against prompt injections and jailbreak attempts in LLMs; pick promptfoo if promptfoo aids in evaluating AI prompts, LLM agents, and RAG systems through declarative config testing with CI/CD support.
Markdown twin · vigil-llm alternatives · promptfoo alternatives
GraphCanon updated 2w
Trust & integrity
| Signal | vigil-llm | promptfoo |
|---|---|---|
| Maintenance | Dormant (901d since push) As of 3w · github_public_v1 | Very active (0d since push) As of 2w · github_public_v1 |
| Provenance | Not a fork · Personal account As of 3w · github_public_v1 | Not a fork · Organization account As of 2w · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of 1mo · osv@v1 | No lockfile (source not queried) As of 1mo · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- vigil-llm
- Detect prompt injections and other risky inputs in LLMs
- promptfoo
- Tool for evaluating prompts and AI agents by comparing performance across various models and red teaming.
Stars
- vigil-llm
- 491
- promptfoo
- 24k
Forks
- vigil-llm
- 56
- promptfoo
- 2.1k
Open issues
- vigil-llm
- 16
- promptfoo
- 481
Language
- vigil-llm
- Python
- promptfoo
- TypeScript
Adopt for
- vigil-llm
- Vigil-llm is designed for users who need robust security measures to protect against prompt injections and jailbreak attempts in LLMs.
- promptfoo
- promptfoo aids in evaluating AI prompts, LLM agents, and RAG systems through declarative config testing with CI/CD support.
Persona
- vigil-llm
- -
- promptfoo
- -
Runtime
- vigil-llm
- -
- promptfoo
- -
License
- vigil-llm
- Apache-2.0
- promptfoo
- MIT
Last pushed
- vigil-llm
- Jan 31, 2024
- promptfoo
- Aug 1, 2026
Categories
- vigil-llm
- Evaluation & Observability
- promptfoo
- Evaluation & Observability, LLM Frameworks
Trust and health
Maintenance
- vigil-llm
- Dormant (18%)
- promptfoo
- Very active (96%)
Days since push
- vigil-llm
- 901d
- promptfoo
- 0d
Open issues (now)
- vigil-llm
- 16
- promptfoo
- 481
Owner type
- vigil-llm
- User
- promptfoo
- Organization
Full report
- vigil-llm
- Trust report
- promptfoo
- Trust report
Typed relationship
Shared compatibility
- Python · vigil-llm: Python runtime · promptfoo: Python runtime
Choose vigil-llm if…
- vigil-llm is primarily Python; promptfoo is TypeScript.
- License: vigil-llm is Apache-2.0, promptfoo is MIT.
- `Vigil` and `PromptFoo` both evaluate LLM inputs, but they do so from different perspectives: security vs. quality/red-teaming.
- Tags unique to vigil-llm: adversarial-attacks, large language models, llm security, prompt-injection.
- When deploying large language models that require high levels of input security, vigil-llm can be employed to detect maliciously crafted inputs intended to manipulate model behavior.
When NOT to use vigil-llm
- If your application does not require high security against malicious inputs or if the risks of prompt injection are minimal due to controlled input sources, vigil-llm might be unnecessary.
- For projects that focus on optimizing output speed rather than input robustness, other tools might be more appropriate as vigil-llm could add significant processing overhead.
Choose promptfoo if…
- promptfoo is primarily TypeScript; vigil-llm is Python.
- License: promptfoo is MIT, vigil-llm is Apache-2.0.
- `Vigil` and `PromptFoo` both evaluate LLM inputs, but they do so from different perspectives: security vs. quality/red-teaming.
- Tags unique to promptfoo: ci-cd, evaluation-framework, llm-evaluation, pentesting.
- Also covers LLM Frameworks.
- For comparing performance across GPT, Claude, Gemini, DeepSeek
When NOT to use promptfoo
- If you do not require comparative analysis among multiple LLM models
- If your project does not benefit from the specific red teaming capabilities offered by promptfoo
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (deadbits/vigil-llm) · observed Jul 21, 2026
- GitHub forks (deadbits/vigil-llm) · observed Jul 21, 2026
- Last push (deadbits/vigil-llm) · observed Jan 31, 2024
- License file (Apache-2.0) · observed Jul 21, 2026
- Decision facts (enrichment) · observed Jul 15, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (promptfoo/promptfoo) · observed Aug 2, 2026
- GitHub forks (promptfoo/promptfoo) · observed Aug 2, 2026
- Last push (promptfoo/promptfoo) · observed Aug 1, 2026
- License file (MIT) · observed Aug 2, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: vigil-llm 491 · promptfoo 24k (synced Jul 21, 2026).
Common questions
- What is the difference between vigil-llm and promptfoo?
- vigil-llm: Detect prompt injections and other risky inputs in LLMs. promptfoo: Tool for evaluating prompts and AI agents by comparing performance across various models and red teaming.. See the comparison table for live GitHub stats and shared categories.
- When should I choose vigil-llm over promptfoo?
- Choose vigil-llm over promptfoo when vigil-llm is primarily Python; promptfoo is TypeScript; License: vigil-llm is Apache-2.0, promptfoo is MIT;
VigilandPromptFooboth evaluate LLM inputs, but they do so from different perspectives: security vs. quality/red-teaming; Tags unique to vigil-llm: adversarial-attacks, large language models, llm security, prompt-injection; When deploying large language models that require high levels of input security, vigil-llm can be employed to detect maliciously crafted inputs intended to manipulate model behavior. - When should I choose promptfoo over vigil-llm?
- Choose promptfoo over vigil-llm when promptfoo is primarily TypeScript; vigil-llm is Python; License: promptfoo is MIT, vigil-llm is Apache-2.0;
VigilandPromptFooboth evaluate LLM inputs, but they do so from different perspectives: security vs. quality/red-teaming; Tags unique to promptfoo: ci-cd, evaluation-framework, llm-evaluation, pentesting; Also covers LLM Frameworks; For comparing performance across GPT, Claude, Gemini, DeepSeek. - When should I avoid vigil-llm?
- If your application does not require high security against malicious inputs or if the risks of prompt injection are minimal due to controlled input sources, vigil-llm might be unnecessary. For projects that focus on optimizing output speed rather than input robustness, other tools might be more appropriate as vigil-llm could add significant processing overhead.
- When should I avoid promptfoo?
- If you do not require comparative analysis among multiple LLM models If your project does not benefit from the specific red teaming capabilities offered by promptfoo
- Is vigil-llm or promptfoo more popular on GitHub?
- promptfoo has more GitHub stars (23,838 vs 491). Stars measure visibility, not whether either tool fits your constraints.
- Are vigil-llm and promptfoo open source?
- Yes - both are open-source projects on GitHub (vigil-llm: Apache-2.0, promptfoo: MIT).
- Where can I find alternatives to vigil-llm or promptfoo?
- GraphCanon lists graph-backed alternatives at vigil-llm alternatives and promptfoo alternatives (vigil-llm markdown twin, promptfoo markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, vigil-llm or promptfoo?
- vigil-llm: Dormant. promptfoo: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for vigil-llm and promptfoo?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: vigil-llm trust report; promptfoo trust report.