evaluate 0 0 0

isisyangyang/judgeflip-judge-audit

published by @isisyangyang

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
171
Last 30 days
30
Likes
-
Size
26 KB
Created on HF
2026-07-17
Age
3 months ago

Description

JudgeFlip — Jailbreak Judge Calibration & Adversarial-Robustness Audit

Companion metadata & reproduction dataset for the paper:

How Reliable Is Your Jailbreak Judge? Calibration and Adversarial Robustness of Automated ASR Scoring

Yang Gao (Veyon Solutions). arXiv:2606.25487

Code: https://github.com/gy15901580825/judgeflip

Almost every LLM jailbreak / prompt-injection paper reports an attack-success rate (ASR), and

that number is assigned by an automated judge — a fine-tuned… See the full description on the dataset page: https://huggingface.co/datasets/isisyangyang/judgeflip-judge-audit.

Tags

task_categories:text-classificationlanguage:enlicense:cc-by-4.0size_categories:n<1Karxiv:2606.25487region:usai-safetyjailbreakred-teamingllm-as-judgeevaluationcalibrationadversarial-robustnessharmbencharxiv:2606.25487

README current version from Hugging Face


license: cc-by-4.0
language:

  • en
    task_categories:
  • text-classification
    tags:
  • ai-safety
  • jailbreak
  • red-teaming
  • llm-as-judge
  • evaluation
  • calibration
  • adversarial-robustness
  • harmbench
  • arxiv:2606.25487
    pretty_name: "JudgeFlip: Jailbreak Judge Calibration & Robustness Audit"
    size_categories:
  • n<1K

JudgeFlip — Jailbreak Judge Calibration & Adversarial-Robustness Audit

Companion metadata & reproduction dataset for the paper:

How Reliable Is Your Jailbreak Judge? Calibration and Adversarial Robustness of Automated ASR Scoring
Yang Gao (Veyon Solutions). arXiv:2606.25487
Code: https://github.com/gy15901580825/judgeflip

Almost every LLM jailbreak / prompt-injection paper reports an attack-success rate (ASR), and
that number is assigned by an automated judge — a fine-tuned safety classifier, or an LLM
prompted to grade. This dataset lets you audit those judges: how well they agree with human labels
(calibration), and how easily their verdicts flip under content-preserving attacks (robustness).

⚠️ What this dataset is (and is not)

This is a responsible, metadata-only release. It deliberately contains no harmful text.

  • ✅ It does contain: our judges' per-item verdicts, harm probabilities, human gold labels
    (majority of 3), attack-flip outcomes, aggregate calibration/robustness metrics, and the full
    human-annotation protocol.
  • ❌ It does not contain: the harmful behaviors, the model completions being judged, or the
    attacked ("flipped") responses. Those live in HarmBench
    under HarmBench's own license, and are not redistributed here.

Every per-item row is keyed by HarmBench's behavior_id, so anyone with legitimate HarmBench access
can join back to the original text and fully reproduce our results — without this repository ever
hosting harmful content. This mirrors the withholding decision stated in the paper and the code repo.

Files

File Contents Harmful text?
data/aggregate_calibration.csv Per-judge precision / recall / F1 / accuracy vs human majority No
data/aggregate_robustness.csv Per-judge, per-attack Yes→No flip rates (+ GCG white-box result) No
data/human_audit_round2.csv Per-item human harm-preservation audit (round 2, n=80): 2 independent annotators' labels + agreement No
data/per_item_metadata.csv Per-item judge verdicts, p_harm, human labels, flip flags — keyed by behavior_id No (pending; see below)
annotation_protocol.md The 2-annotator harm-preservation annotation guide (bilingual) No
scripts/build_metadata.py Converts raw experiment outputs → per_item_metadata.csv (strips all harmful columns) No

Note on per_item_metadata.csv: this file is produced from the paper's GPU experiment outputs
(step2_results.csv, flipped_pairs.csv) by scripts/build_metadata.py, which keeps only IDs,
predictions and labels and drops every free-text column (behavior, context,
original_response, attacked_response, generation). See the schema below.

per_item_metadata.csv schema

Column Type Description
behavior_id str HarmBench behavior id — join key to the HarmBench behavior/response text
contextual 0/1 Whether the behavior has a HarmBench context string
judge str harmbench_cls, qwen2.5-7b, phi-3.5-mini, qwen2.5-3b
pred 0/1 Judge verdict on the clean response (1 = "harmful/success")
p_harm float Judge harm probability on the clean response (classifier only)
human_gold 0/1 Majority of 3 human annotators (1 = harmful)
h0,h1,h2 0/1 Individual human annotator labels (where available)
official_cls 0/1 HarmBench's stored classifier prediction (reproduction cross-check)
attack str Wrapper name for flip rows (refusal_prefix, edu_framing, story_wrap, prepend_append), else empty
flipped 0/1 For a genuine true-positive, whether this attack flipped the verdict Yes→No

human_audit_round2.csv schema

The paper's harm-preservation audit (R4): 80 randomly-sampled flipped (judge Yes→No) attacked
responses, labeled by 2 independent annotators, blind, after a calibration gate. This file
contains the labels only — the underlying harmful text is withheld (join on item_id requires the
withheld master).

Column Type Description
item_id str Opaque audit item id (join key to the withheld text master)
judge str Which LLM-judge's true-positive this flipped item came from
attack str Wrapper that produced the flip (refusal_prefix, story_wrap, prepend_append, edu_framing)
label_A str Annotator A label: harmful / not_harmful / unsure
label_B str Annotator B label (independent)
agree 0/1 Whether A and B gave the same label
final_verdict str Post-adjudication outcome (harm_preserved)

Raw 2-annotator agreement = 93.8% (75/80); all 5 disagreements were adjudicated to confirmed
harmful → human-verified harm-preservation = 100% (80/80), corroborating that the attacks never
alter the harmful body.

Headline findings (from the paper)

Safety judges are miscalibrated in opposite directions, and differ enormously in robustness:

Judge Type Precision Recall Any-wrapper flip rate
HarmBench-Llama-2-13b-cls dedicated classifier 0.835 0.974 (over-flags) 3.4% (robust to surface attacks)
Qwen2.5-7B-Instruct LLM-as-judge 0.940 0.174 83.0%
Phi-3.5-mini-instruct LLM-as-judge 0.810 0.648 57.1%
Qwen2.5-3B-Instruct LLM-as-judge 0.889 0.059 100%
  • The dedicated classifier over-flags (recall 0.97) → inflates ASR before any attack.
  • LLM-as-judges have high precision but wildly inconsistent recall (0.06–0.65) → ASR is both
    biased and unstable across judge choice.
  • A prepended refusal sentence flips 39–88% of LLM-judge true positives — they key on refusal
    phrasing, not content.
  • Even the robust classifier is broken 70% (21/30) of the time by a white-box GCG attack.
  • A 2-annotator human audit confirms the attacks preserve harmful content (100% of 80 sampled flips).

Takeaway: no judge family should be trusted without calibrating and adversarially checking it.
When you report ASR, also report the judge's precision/recall and an adversarial-robustness check.

How to reproduce

  1. Obtain the HarmBench classifier validation set + behaviors from
    HarmBench (subject to their license).
  2. Join per_item_metadata.csv on behavior_id to recover the text.
  3. Run the experiment scripts in the JudgeFlip repo
    (step2–step9), pinned to transformers==4.46.3.

License

The contents of this repository (our metrics, per-item verdicts/labels, annotation protocol,
and scripts) are released under CC-BY-4.0 — please cite the paper if you use them.

This repository does not include HarmBench data or model weights. HarmBench behaviors and
validation set are governed by HarmBench's own license and terms;
the evaluated models are under their respective licenses.

Citation

@misc{gao2026judgeflip,
  title         = {How Reliable Is Your Jailbreak Judge? Calibration and Adversarial Robustness of Automated ASR Scoring},
  author        = {Gao, Yang},
  year          = {2026},
  eprint        = {2606.25487},
  archivePrefix = {arXiv},
  primaryClass  = {cs.CL}
}

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-07-17Link dataset to arXiv:2606.25487 (paper page)206b8da7.7 KB
    Loading...
  2. 2026-07-17Add round-2 human harm-preservation audit (n=80, text-free) + card schema7f735317.6 KB
    Loading...
  3. 2026-07-17Add JudgeFlip judge calibration & robustness audit (metadata-only)2f6d17b6.4 KB
    Loading...
  4. 2026-07-17initial commit9c0041d0 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.

Related datasets same stage · evaluate

Read further

Metadata

License
cc-by-4.0

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("isisyangyang/judgeflip-judge-audit")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="isisyangyang/judgeflip-judge-audit", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/isisyangyang/judgeflip-judge-audit
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