How to cite Provael
Cite release 0.41.2. But the numbers on /results were measured by 0.32.0, and the manifest carrying them is pinned at v0.39.1, commit ae828bf — those are three different versions, and this page keeps them apart.
BibTeX
@software{jain_provael_2026,
author = {Jain, Sattyam},
title = {Provael: red-teaming Vision-Language-Action robot policies in simulation},
version = {0.41.2},
year = {2026},
url = {https://github.com/provael/provael},
doi = {10.5281/zenodo.21984184},
license = {Apache-2.0}
}Rendered from the same fields as CITATION.cff, so the two cannot drift into different versions. Released 2026-09-09.
DOI
DOI: 10.5281/zenodo.21984184
The version you cite is not the version that produced the numbers
They differ today, and they will differ again after any release that ships before the evidence manifest is re-pinned. Quoting the newest release beside figures measured at an older commit is fine — as long as you say which is which.
- Cite this release
- 0.41.2, released
- Numbers on /results and /leaderboard came from
- v0.39.1, commit ae828bf
- Evidence manifest verified
Every public figure on this site derives from that pinned manifest at build time. See the measured result,the leaderboard and verification.
CITATION.cff
GitHub renders it into a "Cite this repository" button, which is the path most people use.
CITATION.cff on GitHubraw file (Citation File Format)
Citing the Embodied AI Security Top 10 separately
The Embodied AI Security Top 10, version 0.2 (2026) —docs/top10.md. Licensed CC-BY-SA-4.0, not Apache-2.0 like the software.
Licensed CC-BY-SA-4.0, not Apache-2.0 like the software. It is a community-draft taxonomy with expert-elicited ranking, and is not affiliated with or endorsed by the OWASP Foundation or MITRE.