toolsSource-backedReview first Safety · Privacy ·

Garak

Open-source LLM vulnerability scanner for probing model behavior, prompt attack surfaces, and safety failures.

by NVIDIA·added 2026-04-27·

CLI

HarnessCLI

Command center

Source

Review first

Review safety and privacy notes before installing or copying commands.

Install & copy

## Editorial notes

Garak is useful for security teams that need repeatable checks for model, prompt, and application-level LLM risks.

## Disclosure

Editorial listing. No paid placement or affiliate link is used.

Trust & readiness

TrustReview first
Sourcesource-backed
Safety notesMissing
ReviewedYes

Community context

Related entries(4)
Related guides(3)
Community signals

Compare

Integrations & API

Contribute

Suggest a metadata change Claim this listing

Documentation Source repository Browse directory

Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL: https://heyclau.de/entry/tools/garak
Source URLs: https://github.com/NVIDIA/garak
Brand: Garak
Brand domain: github.com
Author: NVIDIA
Claim status: unclaimed
Last verified: 2026-04-27

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Required checks are still incomplete. Finish source and safety verification before adopting this resource.

Compare context

Selected

Current score

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
Registry metadata indicates a reviewed listing.
Done

Safety and privacy checks

Required checks missing

Validate risk disclosures before installation or API wiring.

Safety notes presentRequired
No safety notes listed.
Pending
Privacy notes presentRequired
No privacy notes listed.
Pending
Trust level risk gateRequired
Trust level does not block evaluation.
Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Pending
Baseline comparison available
No baseline peer selected yet.
Pending
Diverging trust signals identified
No major trust-signal divergence found.
Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Install command

Not provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

None

Platforms

1 listed

Install type

Copy & paste

Adoption plan

Balanced adoption plan

Current risk score 44/100. Use staged verification before broader rollout.

Risk 44

Adoption blockers

Safety notes are missing.
Privacy notes are missing.

Pre-adoption checks

Validate source and review signals before any execution.

Confirm source provenanceRequired
Source URL/provenance metadata is present.
Done
Confirm metadata review state
Listing has review metadata.
Done
Verify install payload
Install/config payload exists and can be inspected.
Done

Security checks

Confirm safety, privacy, and package integrity signals.

Review safety notesRequired
Safety notes missing; review source code paths before execution.
Pending
Review privacy notesRequired
Privacy notes missing; inspect network/data behavior manually.
Pending
Verify package integrity metadata
No package verification/checksum metadata.
Pending

Rollout

Adopt in controlled steps based on the selected plan.

Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Pending
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Pending
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Safety notes. Risk score 36.

Risk 36

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Missing

Safety notes are missing.

Required in this preset

Privacy notes

Missing

Privacy notes are missing.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Safety notes

Decision timeline

Decision timeline · balanced

Blocking gaps: Review safety notes. Risk 32.

Risk 32

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are missing.

Pending

verify

Review privacy notes

Privacy notes are missing.

Pending

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Review safety notes

Schema details

Install type: copy
Troubleshooting: No

Source repository stats

Scope: Source repo

Tool listing metadata

Website: https://github.com/NVIDIA/garak
Pricing: open-source
Disclosure: editorial
Application category: SecurityApplication
Operating system: macOS, Windows, Linux

Full copyable content

## Editorial notes

Garak is useful for security teams that need repeatable checks for model, prompt, and application-level LLM risks.

## Disclosure

Editorial listing. No paid placement or affiliate link is used.

About this resource

Editorial notes

Garak is useful for security teams that need repeatable checks for model, prompt, and application-level LLM risks.

Disclosure

Editorial listing. No paid placement or affiliate link is used.

#security #red-teaming

Source citations

Source methodology →

Add this badge to your README

Show that Garak is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/tools/garak.svg)](https://heyclau.de/entry/tools/garak)

How it compares

Garak side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field	Garak Open-source LLM vulnerability scanner for probing model behavior, prompt attack surfaces, and safety failures. Open dossier	Giskard AI testing platform for evaluating, scanning, and monitoring machine learning and LLM application quality. Open dossier	Grype Apache-2.0 vulnerability scanner from Anchore for container images, filesystems, archives, SBOMs, PURLs, and CPEs, with risk scoring, VEX filtering, and CI-friendly output. Open dossier	Promptfoo Open-source prompt testing and red-teaming framework for LLM outputs, regressions, evaluations, and security checks. Open dossier
Next steps	Open dossier API JSON Open LLM Open source Newsletter Claim listing	Open dossier API JSON Open LLM Open source Newsletter Claim listing	Open dossier API JSON Open LLM Open source Newsletter Claim listing	Open dossier API JSON Open LLM Open source Newsletter Claim listing
Trust
Review status	ReviewedMaintainer reviewed	ReviewedMaintainer reviewed	ReviewedMaintainer reviewed	ReviewedMaintainer reviewed
Package trust	Package not verified	Package not verified	Package not verified	Package not verified
Source provenance	Source-backed	Source-backed	Source-backed	Source-backed
SubmitterDiffers	—	—	oktofeesh1	—
Install risk	Review first	Review first	Review first	Review first
Notes	Safety · Privacy ·	Safety · Privacy ·	Safety ✓ Privacy ✓	Safety · Privacy ✓
Brand	—	Giskard	Grype	Promptfoo
Category	tools	tools	tools	tools
Source	source-backed	source-backed	source-backed	source-backed
Author	NVIDIA	Giskard	Anchore	Promptfoo
Added	2026-04-27	2026-04-27	2026-06-04	2026-04-27
Platforms	CLI	CLI	CLI	CLI
Source repo	—	—	—	—
Safety notes	— missing	— missing	✓Grype parses container images, archives, filesystems, SBOMs, package identifiers, and vulnerability data; run it from trusted automation with bounded filesystem access and resource limits for untrusted targets. The install script and binary update paths should be verified before use in production CI; pin versions and checksums where reproducible builds or regulated environments require it. Scanning private images can use registry credentials, client certificates, tokens, Docker or Podman daemon access, and local image metadata, so CI jobs should scope credentials and avoid broad registry permissions. Vulnerability findings are advisory and depend on package detection, vulnerability database freshness, distro context, CPE matching, fix-state metadata, EPSS, KEV, and risk-scoring inputs; high-impact findings still need human triage. Fail-on thresholds, only-fixed filters, only-notfixed filters, ignore rules, VEX documents, and suppressed-result settings can change pipeline outcomes, so policy changes should be reviewed like security code. The configuration reference includes options for insecure registry TLS behavior and HTTP registry access; these should be avoided outside tightly controlled test environments. Automatic database updates and application update checks make outbound network requests unless disabled or pinned by policy. Large images, archives, monorepos, or SBOMs can produce expensive scans and large JSON/SARIF artifacts; set timeouts, artifact limits, cache policy, and retention rules in CI.	— missing
Privacy notes	— missing	— missing	✓The Grype getting-started docs say Grype runs locally and does not send scan data to external services; it needs internet access for downloading container images and the vulnerability database. Pulling images from remote or private registries can disclose image names, tags, digests, registry hostnames, platform requests, authentication attempts, and network metadata to registry infrastructure. Scan output can reveal package names, package versions, ecosystems, distro names, image identifiers, file metadata, file digests, executable metadata, vulnerability identifiers, fix versions, EPSS, KEV, risk scores, and suppressed findings. JSON, SARIF, CycloneDX, and template outputs are useful for automation but can leak dependency inventory and security posture when uploaded to CI logs, code scanning tools, tickets, dashboards, or long-retention artifacts. Configuration files and environment variables can include registry usernames, passwords, tokens, client certificates, client keys, CA certificates, cache paths, update URLs, ignore rules, VEX documents, and output paths. SBOM inputs may contain full dependency inventories and build metadata; treat Grype reports and source SBOMs as security-sensitive artifacts.	✓Promptfoo sends your prompts and test inputs to the model providers you configure to run evals and red-team probes; review which providers are used and keep secrets out of test cases.
Prerequisites	— none listed	— none listed	Grype installed from an official or trusted package path such as the Anchore install script, Homebrew, Windows package manager, Docker image, or GitHub release. Target selection for container images, registries, Docker, Podman, containerd, OCI archives, Docker archives, Singularity images, directories, files, SBOMs, Package URLs, or CPEs. Vulnerability database update policy, cache directory, offline scanning expectations, database age policy, and network allowance for database downloads. CI policy for output formats, JSON/SARIF artifacts, fail-on severity thresholds, fix-state filters, VEX documents, ignore rules, and suppressed-result review.	— none listed
Install	—	—	—	—
Config	—	—	—	—
Citations	Source repositorygithub.com 2026-07-13T15:19:32-07:00 Documentationgithub.com Source methodology →	Source repositorygithub.com 2026-07-13T15:19:32-07:00 Documentationdocs.giskard.ai Source methodology →	Source repositorygithub.com 2026-07-13T15:19:32-07:00 Documentationoss.anchore.com Submitted by oktofeesh12026-06-04 Source methodology →	Source repositorygithub.com 2026-07-13T15:19:32-07:00 Documentationpromptfoo.dev Source methodology →
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed