🔎
garak
  • 👋Welcome to garak!
  • Overview
    • 💡What is garak?
    • ✨Our Features
  • LLM scanning basics
    • 🔐What is LLM security?
    • 🛠️Setting up
      • 😇Installing garak
      • 🐍Installing the source code
    • 🚀Your first scan
    • 🔮Reading the results
  • Examples
    • ☑️Basic test
    • 💉Prompt injection
    • ☢️Toxicity generation
    • 🗝️Jailbreaks
    • 💱Encoding-based bypass
    • 📼Data leaks & replay
    • 🤦False reasoning
    • 🛀Automatic soak test
  • garak components
    • 🕵️‍♀️Vulnerability probes
    • 🦜Using generators
    • 🔎Understanding detectors
    • 🏇Managing it: harnesses
    • 💯Scan evaluation
  • Automatic red-teaming
    • 🔴What is red-teaming?
    • 🤼Responsive auto-prompt
    • 🪖garak's auto red-team
    • 🏞️Red teaming in the wild
  • Going further
    • ❓FAQ
    • 💁Getting help
    • 🎯Reporting hits
    • 🧑‍🤝‍🧑Contributing to garak
Powered by GitBook
On this page
  1. garak components

Vulnerability probes

The big important part of garak is its big collection of probes. Each probe is designed to detect a single kind of vulnerability. The probes interact directly with the language model, sometimes sending up to thousands of prompts. The language model - represented with in garak with a "generator" - generates output text in response to the probe's prompts.

Probes have complete control of the interaction with the generator, and so can do a lot of different things. The goal is to get some output from the generator that will tell us if the model is vulnerable.

PreviousAutomatic soak testNextUsing generators

Last updated 1 year ago

🕵️‍♀️