Standard Bots RO1 Robotics API. # noqa: E501
Metadata
Release files for standardbots 2.20260731.60
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 | |
|---|---|---|---|---|
| standardbots-2.20260731.60.tar.gz | 96.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| standardbots-2.20260731.60-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 172.8 kB
Release files / standardbots-2.20260731.60.tar.gz
| Download URL | standardbots-2.20260731.60.tar.gz |
|---|---|
| Size | 96.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a01adbb545b6ceaffd1f83bb3185c5ef6cb5e64f626efd66aeb5e17c2709d9be
|
|
BLAKE2b-256 checksum How to use checksums |
8bff8cccec4279e8f0d4581817d4617248d84f164e7fbb059a2b837198d7740e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / standardbots-2.20260731.60-py3-none-any.whl
| Download URL | standardbots-2.20260731.60-py3-none-any.whl |
|---|---|
| Size | 76.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02e83500b1f1b990161fdd10beb2b44cfcdc0f2b7877fc51fac8dc2524af45d1
|
|
BLAKE2b-256 checksum How to use checksums |
f6f816abcaf29de0526390a380387c0b3158175bd3ecbe72c3a321d5aacfe781
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for standardbots 2.20260731.60
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.