Standard Bots RO1 Robotics API. # noqa: E501
Metadata
Release files for standardbots 2.20260921.40
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.40.tar.gz | 113.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| standardbots-2.20260921.40-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 200.8 kB
Release files / standardbots-2.20260921.40.tar.gz
| Download URL | standardbots-2.20260921.40.tar.gz |
|---|---|
| Size | 113.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
98021ba43f065ffafbaeb031eab3873075abc35a97dd8bcd9603159bbea55532
|
|
BLAKE2b-256 checksum How to use checksums |
0c7b3bd79fee6e359816a8151446d20493674ad64faa7412e98599e5d1365299
|
| 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.40-py3-none-any.whl
| Download URL | standardbots-2.20260921.40-py3-none-any.whl |
|---|---|
| Size | 87.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
72cac889f7b487ebbf050f4c239d898613033a708db5ed242eb7e30336dc715d
|
|
BLAKE2b-256 checksum How to use checksums |
12c191e4137f4ba90bcdeecc6e824496ed0d517f72d9a89abee0fa63d3379d02
|
| 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.40
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.