GOVERNATLAS / PRODUCT DOSSIER

garak

The garak project documents an LLM vulnerability scanner using probes and output detectors to examine model behavior.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Select the generator, probes and detectors before interpreting a scan. A detector classifies a model output under particular conditions; it does not prove that every downstream application action is safe. Define the permitted target and retain failed requests and missing observations alongside any detected issue.

What this record does not establish

Probe results depend on selected generators, detectors and execution conditions. A completed scan does not establish comprehensive security or equivalence to runtime enforcement.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

Run a proposed authorized trial only against a synthetic or explicitly permitted target. Preserve configuration, probe identity, output reference and detector decision. Include a benign control and one unavailable dependency, then replay a selected case without assuming that a different model or application shares the result.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. A generator/probe/detector configuration and authorization record.
  2. An interpretable result set with failed and inconclusive observations retained.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

01
vendor asserted

The garak project documents an LLM vulnerability scanner using probes and output detectors to examine model behavior. Scope: primary documentation only; no independent product test or compliance determination.

Source, dates & preserved provenancegarak — current primary product documentation ↗

Authority: vendor owned
Observed 2026-10-16 · Reviewed 2026-10-16 · current until 2026-11-15

Artifact SHA-256: 45a8954a409e8fa63dc5bdd8bec6746dd52dffa58476a4f234595ea5a1b828bf

The hash identifies the preserved capture. The live source may have changed.

Source register

garak — current primary product documentation ↗vendor owned · captured 2026-10-16
Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

01

Can you provide a generator/probe/detector configuration and authorization record for the selected configuration?

02

Can you provide an interpretable result set with failed and inconclusive observations retained for the selected configuration?

03

Which exact version, entitlements, data paths and responsible roles apply?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗