Giskard v3 is here! #2814
kevinmessiaen
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🎉 Giskard v3 is now available. 🎉
This release rebuilds Giskard around a simpler goal: help developers test, evaluate, and red-team AI agents with focused Python packages and a lightweight, async-first architecture.
Build repeatable agent evaluations
Use Giskard Checks to describe single-turn or multi-turn scenarios, run them against synchronous or asynchronous targets, and evaluate the resulting trace with deterministic checks or LLM judges.
Checks can cover exact and semantic matching, groundedness, conformity, JSON validity, readability, custom assertions, and more. Scenarios can be grouped into suites, run in parallel, and exported as JUnit reports for CI/CD.
Generate security and quality tests
Use Giskard Scan and
vulnerability_scanto generate adversarial scenarios for risks such as prompt injection, jailbreaks, harmful content, stereotypes, and misinformation.For RAG systems,
quality_scanwith a knowledge base generates and evaluates knowledge-base quality scenarios. Generated suites can also be replayed in CI.Try it out
The base package installs Giskard Checks:
Add Scan for vulnerability and quality scanning, and install the provider extra required by any LLM-backed checks or generators:
See the Checks installation guide or Scan installation guide for provider setup.
A new architecture
v3 is organized as five focused libraries:
giskard-checksfor agent testing and evaluationgiskard-scanfor vulnerability and RAG-quality scanninggiskard-agentsfor agent and workflow orchestrationgiskard-llmfor provider-agnostic LLM routinggiskard-corefor shared utilitiesEach package carries only the dependencies it needs, so projects can install the capabilities they use without bringing in the full stack.
Migrating from v2
v3 is a full rewrite rather than an in-place API upgrade, check out the [v2-to-v3 migration] guide(https://docs.giskard.ai/oss/migrate-from-v2).
The automatic tabular/ML scan and the legacy @giskard.testing` suite remain v2-only. If you rely on those workflows, keep that part of your project on v2:
pip install "giskard[llm]>2,<3"Giskard v2 remains available but is no longer actively maintained.
Start testing
All reactions