vla-robustness-kit
vla-robustness-kit generates deterministic, simulator-free perturbation
diagnostics over episode instructions, metadata, and task-phase lists.
At a Glance
| Job | Exercise a robustness-report pipeline across language, vision metadata, embodiment metadata, and phase-order variants. |
| Built for | VLA evaluation developers and robotics teams prototyping review workflows. |
| Differentiator | Runs without a simulator, GPU, robot, image transformation, or model service. |
| Produces | Markdown pass rates, failure clusters, and follow-up data collection recommendations. |
Install
python -m pip install "vla-robustness-kit==0.1.2"
Verified Quickstart
Run from a source checkout:
vla-robustness-kit run examples/mock_episode_set \
--policy mock \
--out /tmp/vla-robustness-report.md
The bundled fixture emits 22 deterministic perturbation trials and a Markdown diagnostic report.
What Is Actually Perturbed
- language instruction strings;
- lighting and camera-pose metadata;
- control-rate and coordinate-frame metadata;
- task-phase ordering.
The standalone CLI currently accepts only --policy mock. The bundled mock
policy assigns deterministic pass/fail outcomes from variant names and fixture
tags. It does not invoke a VLA model or inspect image pixels.
LeRobot and RLDS helper modules normalize selected metadata fields for callers,
but the CLI reads an episodes.jsonl file or a directory containing that file.
Runtime, Data, and Network Boundary
- The CLI reads local JSONL and writes Markdown locally or to stdout.
- It does not make network requests, run a simulator, use a GPU, access robot hardware, or call a model.
- No redaction is applied. Instructions, metadata values, and episode IDs can appear in downstream trial data, so sanitize inputs before sharing.
- Pass rates from the mock policy validate the diagnostic plumbing only. They are not evidence of policy robustness or robot safety.
Limitations
- The standalone CLI currently supports only the bundled mock policy and metadata-level perturbations. It does not transform images or execute a VLA.
- Reports diagnose the supplied fixture or episode set only. They are not benchmark scores, simulator results, or safety guarantees.
Compatibility
robostudio-engine exposes a direct robostudio probe integration. Its wrapper
can run the bundled mock policy or an explicitly supplied local executable
adapter; that BYO executable path is an engine feature, not a capability of the
standalone vla-robustness-kit CLI.
Publication Status
Verified on 2026-07-13:
- PyPI:
vla-robustness-kit==0.1.2 - GitHub release:
v0.1.2 - Bundled reports are deterministic tutorial diagnostics, not benchmark or deployment evidence.
Next Action
Use the mock policy to validate report ingestion and review, then connect a
separately reviewed executable policy adapter through robostudio-engine for
real model outputs.
Metadata
Release files for vla-robustness-kit 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vla_robustness_kit-0.1.2.tar.gz | 9.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vla_robustness_kit-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.3 kB
Release files / vla_robustness_kit-0.1.2.tar.gz
| Download URL | vla_robustness_kit-0.1.2.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e62c29727b585a36fd51f6adef73dbd3ef33ba1a92bcffee707d7f6876e31ef
|
|
BLAKE2b-256 checksum How to use checksums |
a8393f072705f2f77f6c47a3f0fc65f482cc16e5b3910f4659c6307aacd6f61b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.
Transparency logRelease files / vla_robustness_kit-0.1.2-py3-none-any.whl
| Download URL | vla_robustness_kit-0.1.2-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eee113fcd3c89833cd6455407e11f61c4771492fa5c390ca86f6fdeb0c77b324
|
|
BLAKE2b-256 checksum How to use checksums |
92e1f812b2daf8f71742ec1fc58d88c0ed1ff530d423426c6f1a541a3d9864eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.
Transparency log