Standard Bots RO1 Robotics API. # noqa: E501
Metadata
Release files for standardbots 2.20260731.57
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.57.tar.gz | 96.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| standardbots-2.20260731.57-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 172.8 kB
Release files / standardbots-2.20260731.57.tar.gz
| Download URL | standardbots-2.20260731.57.tar.gz |
|---|---|
| Size | 96.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00f6f08bcf2db9da5d7fc7e42189b01e154259492041b4722715164c83b6e3a2
|
|
BLAKE2b-256 checksum How to use checksums |
14513b94e2d57926e2e74172b846eddccbf86bc74f46c200b953473816a822bb
|
| 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.57-py3-none-any.whl
| Download URL | standardbots-2.20260731.57-py3-none-any.whl |
|---|---|
| Size | 76.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef1b308045b6d3e7a303377c334412b0f8f79b939c05c1ec0b0b340bfff36caf
|
|
BLAKE2b-256 checksum How to use checksums |
4106b9d8cece9b9899ddd878a6555b8c9df08a3c6812b03cd798f33432032fe1
|
| 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.57
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.