This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Embodied First Exam
Code agents program robots in simulation: embodied-first-exam.ai, github.com/mll-lab-nu/embodied-first-exam.
# needs git and Docker with Compose; GPU tasks also need an NVIDIA GPU and the NVIDIA Container Toolkit
uv tool install embodied-first-exam --with-executables-from harbor
# your API keys: in the shell, or in a .env file in the working directory
# the core set; the tasks are cloned on first use (a clone you run from, or $EFE_ROOT, is used instead)
harbor run -d embodied-first-exam -a codex -m openai/gpt-6-astra
This installs Harbor 0.23.0 with the benchmark's flags on harbor run and the efe command. The tasks are not in
the package: see the repository's README.
1 maintainer
Metadata
1 maintainer
Release files for embodied-first-exam 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| embodied_first_exam-1.0.0.tar.gz | 11.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| embodied_first_exam-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.5 kB
Release files / embodied_first_exam-1.0.0.tar.gz
| Download URL | embodied_first_exam-1.0.0.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33caee408af1eb94fcbccc32166a7df9e38582e3ff6ae0b6b6d940bec3d6a94d
|
|
BLAKE2b-256 checksum How to use checksums |
60d1c089ad06147d1b545494db83659a50be3dd3dfba4612aa4ce00833aeb9f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logRelease files / embodied_first_exam-1.0.0-py3-none-any.whl
| Download URL | embodied_first_exam-1.0.0-py3-none-any.whl |
|---|---|
| Size | 12.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f9bf24e7f08266394fa5347e8f5b11f64218cfbaed17297eef9e3627844c9eae
|
|
BLAKE2b-256 checksum How to use checksums |
cc5cb2cac0a1f29dc77f661a6dae7ea38f0586b7b403d931e3491a41966c2c21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logSecurity for embodied-first-exam 1.0.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for embodied_first_exam-1.0.0.tar.gz
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 Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
