Tool for adding mocap to mujoco models
Metadata
Release files for mujoco-mocapper 0.0.1
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 | |
|---|---|---|---|---|
| mujoco-mocapper-0.0.1.tar.gz | 3.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mujoco_mocapper-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.2 kB
Release files / mujoco-mocapper-0.0.1.tar.gz
| Download URL | mujoco-mocapper-0.0.1.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bbc58d48909e1ff93b4e90a958e7e540762d2f1a68274ab74bec60a693692ab5
|
|
BLAKE2b-256 checksum How to use checksums |
350c30e30275cae00fd562ae6dd9bd57609f2891418ae2eb0d999215b14920c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / mujoco_mocapper-0.0.1-py3-none-any.whl
| Download URL | mujoco_mocapper-0.0.1-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93965ab2e96b82857eff454a2f89b7437877e5299deba8a125588a322c10d1cc
|
|
BLAKE2b-256 checksum How to use checksums |
8a82a939c0d75909e9d07778c713e892197c4cae5be8f3a2ab6aed5f28541bb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for mujoco-mocapper 0.0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.