Standard Bots RO1 Robotics API. # noqa: E501
Metadata
Release files for standardbots 2.20260731.58
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.58.tar.gz | 96.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| standardbots-2.20260731.58-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 172.8 kB
Release files / standardbots-2.20260731.58.tar.gz
| Download URL | standardbots-2.20260731.58.tar.gz |
|---|---|
| Size | 96.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffaf210beed1f44a1ed7ecde541095064d8a09f27977d80e06705653690b2461
|
|
BLAKE2b-256 checksum How to use checksums |
6b40fbb17785a4ffd61a77036caf8a3b1c1585dd6e4ca42c92034ca31a9d6b23
|
| 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.58-py3-none-any.whl
| Download URL | standardbots-2.20260731.58-py3-none-any.whl |
|---|---|
| Size | 76.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ceb67645e28b72dcf0cd3974853fe6d28085aa8e3520cf60f95f43c20fa21aef
|
|
BLAKE2b-256 checksum How to use checksums |
809e256f8c69e6ab4cc0692e9ed3266bc330d59fe28b4582b8bad539f19ae469
|
| 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.58
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.