Standard Bots RO1 Robotics API. # noqa: E501
Metadata
Release files for standardbots 2.20260921.50
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.50.tar.gz | 113.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| standardbots-2.20260921.50-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 200.8 kB
Release files / standardbots-2.20260921.50.tar.gz
| Download URL | standardbots-2.20260921.50.tar.gz |
|---|---|
| Size | 113.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a6a2e051119d0f787958617386e45adcdb32825ba970b43dfb8659ad28f8775b
|
|
BLAKE2b-256 checksum How to use checksums |
02f883ee7083765cbe874ac72db9bae7081872b3ca9fdb4076ef0fc80c3f0620
|
| 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.50-py3-none-any.whl
| Download URL | standardbots-2.20260921.50-py3-none-any.whl |
|---|---|
| Size | 87.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44c810c33bab7ca8100bcb9f75261b426720a13c78f6390fef0c80505e15c527
|
|
BLAKE2b-256 checksum How to use checksums |
9838b2783eae2b2199527b537f7af7446b61fc5935d6e798a0515dc400b6ffe8
|
| 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.50
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.