Comparison
vigil-llm vs AgentGuard
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 AgentGuard if agentGuard is a budget-conscious observer for real-time token spending by AI agents and LLMs, integrating with major providers like OpenAI and Anthropic.
Markdown twin · vigil-llm alternatives · AgentGuard alternatives
GraphCanon updated Sep 20, 2026
5views this month
vs
Trust & integrity
| Signal | vigil-llm | AgentGuard |
|---|---|---|
| Maintenance | Dormant (962d since push) As of Sep 20, 2026 · github_public_v1 | Dormant (407d since push) As of Sep 12, 2026 · github_public_v1 |
| Provenance | Not a fork · Personal account As of Sep 20, 2026 · github_public_v1 | Not a fork · Personal account As of Sep 12, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Jul 11, 2026 · osv@v1 | Published findings As of Jul 15, 2026 · 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
- AgentGuard
- Real-time guardrail that monitors token spend and manages LLM/agent loops in real time
Stars
- vigil-llm
- 496
- AgentGuard
- 173
Forks
- vigil-llm
- 56
- AgentGuard
- 11
Open issues
- vigil-llm
- 16
- AgentGuard
- 2
Language
- vigil-llm
- Python
- AgentGuard
- JavaScript
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.
- AgentGuard
- AgentGuard is a budget-conscious observer for real-time token spending by AI agents and LLMs, integrating with major providers like OpenAI and Anthropic.
Persona
- vigil-llm
- -
- AgentGuard
- -
Runtime
- vigil-llm
- -
- AgentGuard
- -
License
- vigil-llm
- Apache-2.0
- AgentGuard
- MIT
Last pushed
- vigil-llm
- Jan 31, 2024
- AgentGuard
- Jul 31, 2025
Categories
- vigil-llm
- Evaluation & Observability
- AgentGuard
- Evaluation & Observability, Inference & Serving
Trust and health
Days since push
- vigil-llm
- 962d
- AgentGuard
- 407d
Open issues (now)
- vigil-llm
- 16
- AgentGuard
- 2
Stars delta
- vigil-llm
- +5 (30d)
- AgentGuard
- +2 (30d)
Open issues delta
- vigil-llm
- 0 (30d)
- AgentGuard
- +1 (30d)
OSV dependency advisories
- vigil-llm
- No lockfile (source not queried)
- AgentGuard
- Published findings
Full report
- vigil-llm
- Trust report
- AgentGuard
- Trust report
Choose vigil-llm if…
- vigil-llm is primarily Python; AgentGuard is JavaScript.
- License: vigil-llm is Apache-2.0, AgentGuard is MIT.
- Tags unique to vigil-llm: adversarial-attacks, large-language-models, llm-security, prompt-injection.
- vigil-llm ships Docker support for self-hosted deployment.
- 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 AgentGuard if…
- AgentGuard is primarily JavaScript; vigil-llm is Python.
- License: AgentGuard is MIT, vigil-llm is Apache-2.0.
- Tags unique to AgentGuard: ai-agents, anthropic, cost-monitoring, observability.
- Also covers Inference & Serving.
- When you need precise control over spend and want live updates on token prices
When NOT to use AgentGuard
- If you prioritize a different language for your project and cannot use JavaScript
- In cases requiring more elaborate fallback mechanisms than what AgentGuard offers
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 Sep 20, 2026
- GitHub forks (deadbits/vigil-llm) · observed Sep 20, 2026
- Last push (deadbits/vigil-llm) · observed Jan 31, 2024
- License file (Apache-2.0) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 15, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (dipampaul17/AgentGuard) · observed Sep 20, 2026
- GitHub forks (dipampaul17/AgentGuard) · observed Sep 20, 2026
- Last push (dipampaul17/AgentGuard) · observed Jul 31, 2025
- License file (MIT) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
GitHub stars on cards: vigil-llm 496 · AgentGuard 173 (synced Sep 20, 2026).
Common questions
- What is the difference between vigil-llm and AgentGuard?
- vigil-llm: Detect prompt injections and other risky inputs in LLMs. AgentGuard: Real-time guardrail that monitors token spend and manages LLM/agent loops in real time. See the comparison table for live GitHub stats and shared categories.
- When should I choose vigil-llm over AgentGuard?
- Choose vigil-llm over AgentGuard when vigil-llm is primarily Python; AgentGuard is JavaScript; License: vigil-llm is Apache-2.0, AgentGuard is MIT; Tags unique to vigil-llm: adversarial-attacks, large-language-models, llm-security, prompt-injection; vigil-llm ships Docker support for self-hosted deployment; 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 AgentGuard over vigil-llm?
- Choose AgentGuard over vigil-llm when AgentGuard is primarily JavaScript; vigil-llm is Python; License: AgentGuard is MIT, vigil-llm is Apache-2.0; Tags unique to AgentGuard: ai-agents, anthropic, cost-monitoring, observability; Also covers Inference & Serving; When you need precise control over spend and want live updates on token prices.
- 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 AgentGuard?
- If you prioritize a different language for your project and cannot use JavaScript In cases requiring more elaborate fallback mechanisms than what AgentGuard offers
- Is vigil-llm or AgentGuard more popular on GitHub?
- vigil-llm has more GitHub stars (496 vs 173). Stars measure visibility, not whether either tool fits your constraints.
- Are vigil-llm and AgentGuard open source?
- Yes - both are open-source projects on GitHub (vigil-llm: Apache-2.0, AgentGuard: MIT).
- Where can I find alternatives to vigil-llm or AgentGuard?
- GraphCanon lists graph-backed alternatives at vigil-llm alternatives and AgentGuard alternatives (vigil-llm markdown twin, AgentGuard 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 AgentGuard?
- vigil-llm: Dormant. AgentGuard: Dormant. 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 AgentGuard?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: vigil-llm trust report; AgentGuard trust report.