Workhorse evals

Most catalog entries map to exactly one category and one insurance exposure. Ranking by how many distinct categories and exposures an eval suite’s entries span surfaces the rare cases where the field leans on one underlying suite across many fronts, rather than the hundreds of standalone, single-purpose tools and benchmarks that make up the rest of the catalog.

#Eval suiteCatalog entriesCategoriesExposures
1inspect_evals19107
20DIN AI Scanner111
33CB (Catastrophic Cyber Capabilities Benchmark)111
4A.I.G (AI-Infra-Guard)111
5A.S.E (AICGSecEval)111
6A2A Scanner111
7ACES (Agent Capability Evaluation Suite)111
8Adversarial Robustness Toolbox (ART)111
9Aegis 2.0 / Nemotron Content Safety V2111
10Agent Governance Toolkit111

Beyond the top one or two suites, entries and counts tie at the minimum (one category, one exposure) — that tie is the honest shape of the data, not a ranking we smoothed over.


Possible duplicates

The same benchmark sometimes appears more than once under a different name or repo — most often an original implementation and a port into another harness (e.g. an Inspect port). These are grouped below as related, not merged or deleted: when we weren’t confident two entries were the same benchmark, we left them as separate, unrelated rows.

  • RE-BenchAutonomy, R&D & self-replication · Unmapped · METR/RE-Bench
  • RE-Bench (Inspect port)Autonomy, R&D & self-replication · Unmapped · METR/inspect-tasks-public

Wanich Risk Lab, 2026.