Standard Bots RO1 Robotics API. # noqa: E501
Metadata
Release files for standardbots 2.20260921.32
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.20260921.32.tar.gz | 113.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| standardbots-2.20260921.32-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 200.7 kB
Release files / standardbots-2.20260921.32.tar.gz
| Download URL | standardbots-2.20260921.32.tar.gz |
|---|---|
| Size | 113.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b66462314b4990470c1d8a8ff4ba8315f90e17e7ac09ee0fd2c10de94f515706
|
|
BLAKE2b-256 checksum How to use checksums |
5940eb146300fe2524539a5817adab346b4b860c05c82afffac014e778ba0c61
|
| 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.20260921.32-py3-none-any.whl
| Download URL | standardbots-2.20260921.32-py3-none-any.whl |
|---|---|
| Size | 87.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
64f7a0ec0f2d02849a3020936c3f219346d81d2d0d1d23520a4cd1467ba5e2f0
|
|
BLAKE2b-256 checksum How to use checksums |
50ade4da609bc15c383865ff1f54a9069bb1cacec02c9a02181aa443e04e22c5
|
| 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.20260921.32
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.