Leaderboard

Ranked by safety, not by success.

Safety is the share of episodes that satisfy every safety specification applicable to the task — not a success rate. Ranking by it rather than by SR is the point: the note under each SR shows where that policy would place on a success-only board, and the two orders do not agree. The full definitions are below.

SR ↑ native task success SBU ↓ successes that still violate a spec VSI ↓ severity of the worst violation

24
policies evaluated
5
evaluation suites
22,500
episodes scored
8
safety specifications
2026-09-26
last updated

RoboCasa-365 · Atomic-Seen

# Model Safety ↑ SR ↑ SBU ↓ VSI ↓
🥇RLDX-1-FT-RC36553.1%58.4%#4 by SR24.0%0.222
🥈GigaWorld-Policy-0.152.0%43.1%#7 by SR20.0%0.255
🥉π0.551.2%42.3%#8 by SR19.8%0.195
4PRTS51.2%64.1%#3 by SR30.4%0.241
5GR00T-N1.651.0%53.6%#5 by SR24.6%0.253
6Xiaomi-Robotics-150.1%81.9%#1 by SR37.7%0.233
7WorldDreamer48.9%68.3%#2 by SR31.1%0.276
8π044.1%32.4%#9 by SR12.3%0.318
9GR00T-N1.540.7%47.2%#6 by SR26.3%0.268

LIBERO · mean over four suites

# Model Train Safety ↑ SR ↑ SBU ↓ VSI ↓
🥇VLA-AdapterSFT82.0%97.6%#3 by SR17.0%0.104
🥈InternVLA-M1SFT81.5%96.4%#10 by SR16.8%0.118
🥉VLANeXtSFT81.5%97.6%#4 by SR17.1%0.110
4X-VLASFT81.0%97.2%#5 by SR17.1%0.113
5MolmoAct2SFT80.9%97.9%#1 by SR17.5%0.107
6SimVLASFT80.2%96.9%#8 by SR18.2%0.123
7OpenVLA-OFT-7BSFT80.1%97.8%#2 by SR18.1%0.122
8UniVLASFT79.5%94.8%#12 by SR17.1%0.127
9GR00T-N1.6SFT78.4%97.1%#6 by SR20.0%0.125
10RIPT-VLA-7BRL78.2%97.1%#7 by SR20.0%0.122
11π0.5SFT77.6%96.6%#9 by SR21.4%0.147
12π0SFT77.5%93.9%#14 by SR19.2%0.140
13OpenVLA-7BSFT77.4%69.4%#18 by SR10.8%0.174
14Cosmos-Policy-2BSFT77.1%95.2%#11 by SR21.5%0.147
15π-RL-130RL76.4%93.0%#15 by SR20.0%0.135
16SmolVLASFT72.9%73.2%#17 by SR11.9%0.206
17GR00T-N1.7SFT72.0%94.2%#13 by SR24.0%0.169
18π0-FASTSFT71.8%86.6%#16 by SR15.0%0.214

Ranked on unrounded Safety, so rows that tie on screen need not tie in the ordering. Every LIBERO row runs 200 rollouts per suite (10 tasks × 20 episodes); every RoboCasa-365 row runs 900 (18 task families × 50 episodes). The RoboCasa-365 policies come from two independently seeded groups (π0, π0.5, GR00T-N1.5 and RLDX-1-FT-RC365 share one seed sequence), so comparisons across the groups are unpaired.

What is scored

RoboCasa-365 atomic-seen covers 18 kitchen task families at 50 episodes each; LIBERO covers four tabletop suites. Policies run through their native inference wrappers with fixed seeds, so the success rate reported here is the one the policy's own harness produces — we add the safety layer on top rather than re-implementing the task.

The four numbers

SR is the benchmark's native success rate. Safety is the fraction of all episodes satisfying every applicable STL specification. SBU (Succ-But-Unsafe) is the fraction of episodes that both succeed and violate — the failures an SR-only evaluation cannot see. VSI is a bounded worst-violation depth, so a policy can have few unsafe successes and still score badly when the violations it does commit are severe.

Submitting a result

Open a pull request against SafeVLA-Bench-release adding one JSON file under submissions/ with your policy name, the benchmark and suite, episode count, and the per-episode verdict file produced by scripts/compute_stl_robustness.py. We re-score from the raw trajectories rather than taking reported numbers, so please include the per-step logs or a link to them. Entries currently on this board were all evaluated by us.

Scores come from the same aggregate the paper reads, regenerated by scripts/make_leaderboard.py. RoboCasa-365 verdicts were recomputed from the per-step force traces in September 2026; earlier numbers derived from the action log alone understated contact violations. See the paper for the specification library and threshold sensitivity analysis.