evaluate 0 0 0

giskardai/harmbench-scenarios

published by @giskardai

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
1.2K
Last 30 days
293
Likes
-
Size
580 KB
Created on HF
2026-06-24
Age
3 months ago

Description

HarmBench Scenarios

Safety-evaluation scenarios derived from the HarmBench behavior dataset, serialized as giskard Scenario objects (one JSON object per line).

Each row poses a harmful request the agent should refuse or safely decline, paired with an LLMJudge check (giskard.scan::judges/harmbench_safety.j2) that grades the agent response.

Format

Every line is a serialized giskard.checks.Scenario:

name — "HarmBench #<id>"

steps[].interacts[].inputs — the harmful… See the full description on the dataset page: https://huggingface.co/datasets/giskardai/harmbench-scenarios.

Tags

source_datasets:walledai/HarmBenchlanguage:enlicense:mitsize_categories:n<1Kformat:jsonmodality:textlibrary:datasetslibrary:pandaslibrary:polarslibrary:mlcroissantarxiv:2402.04249region:ussafetyred-teamingllm-evaluationrefusalharmbench

README current version from Hugging Face


license: mit
language:

  • en
    tags:
  • safety
  • red-teaming
  • llm-evaluation
  • refusal
  • harmbench
    pretty_name: HarmBench Scenarios
    source_datasets:
  • walledai/HarmBench
    configs:
  • config_name: en
    data_files:
    • split: test
      path: harmbench.en.jsonl

HarmBench Scenarios

Safety-evaluation scenarios derived from the HarmBench behavior dataset, serialized as giskard Scenario objects (one JSON object per line).

Each row poses a harmful request the agent should refuse or safely decline, paired with an LLMJudge check (giskard.scan::judges/harmbench_safety.j2) that grades the agent response.

Format

Every line is a serialized giskard.checks.Scenario:

  • name — "HarmBench #<id>"
  • steps[].interacts[].inputs — the harmful prompt sent to the agent under test (dataset_input). Contextual rows prepend the HarmBench context string using {context}\n\n---\n\n{behavior}.
  • steps[].checks[].prompt_path — giskard.scan::judges/harmbench_safety.j2
  • annotations — behavior, functional_category, semantic_category, optional context and tags
  • tags — dataset:harmbench, threat-type:harmful-content-generation, plus functional/semantic category tags

The en config has 400 scenarios in a single test split (evaluation-only, no training data):

Functional category Count
standard 200
contextual 100
copyright 100

License & Attribution

This derivative is released under MIT and may be used commercially.

The source behavior prompts come from walledai/HarmBench (MIT). Please credit the original authors using the citation below.

Citation

@article{mazeika2024harmbench,
  title={HarmBench: A Standardized Evaluation Framework for Automated Red Teaming and Robust Refusal},
  author={Mantas Mazeika and Long Phan and Xuwang Yin and Andy Zou and Zifan Wang and Norman Mu and Elham Sakhaee and Nathaniel Li and Steven Basart and Bo Li and David Forsyth and Dan Hendrycks},
  year={2024},
  eprint={2402.04249},
  archivePrefix={arXiv},
  primaryClass={cs.LG}
}

README history 4 revisions

Every night we snapshot the README of every dataset in the catalog. When the SHA changes we archive the new version and diff it against the last. This is the evolving thought record of the alignment-data field: what the author decided to say about the corpus, and how that framing shifted over time.

  1. 2026-06-24Update README: judge prompt lives in giskard.scan2fa27d52.2 KB
    Loading...
  2. 2026-06-24Point HarmBench judge prompt to giskard.scan5be07f42.2 KB
    Loading...
  3. 2026-06-24Add HarmBench giskard Scenario JSONL dataset (en, 400 rows)1586ff42.2 KB
    Loading...
  4. 2026-06-24initial commita0c086c0 B
    Loading...

Used by abliterated models none yet

No abliterated models in our catalog have declared this dataset in their YAML metadata yet. This can mean the dataset is used but not declared, is used outside abliteration workflows, or is new. The link will populate automatically as models are indexed.

Community discussions 1 thread · 1 open · 1 comments

Threads posted by the community on Hugging Face: bug reports, questions about usage, pull requests on the README, license clarifications. Click any thread to expand and read the full conversation inline. Newest first.

  1. 2026-06-25[bot] Conversion to Parquetopen1 💬#1
    Loading...

Related datasets same stage · evaluate

Read further

Metadata

License
mit

Repository

Download the dataset

0

Copy any of these snippets into your notebook or terminal. All three fetch directly from Hugging Face using your own credentials.

Recommended: datasets library (Python)
from datasets import load_dataset
ds = load_dataset("giskardai/harmbench-scenarios")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="giskardai/harmbench-scenarios", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/giskardai/harmbench-scenarios
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration