Standard Bots RO1 Robotics API. # noqa: E501
Metadata
Release files for standardbots 2.20260921.37
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.37.tar.gz | 113.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| standardbots-2.20260921.37-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 200.7 kB
Release files / standardbots-2.20260921.37.tar.gz
| Download URL | standardbots-2.20260921.37.tar.gz |
|---|---|
| Size | 113.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
51b7a31882b18ce6fc2b24742497709065bcc66863254c1ab3753f2ef6c6e543
|
|
BLAKE2b-256 checksum How to use checksums |
9c5b4eea850f675164cdf50f27b1738fe3ab6681575f290202f1115f3ab21eb6
|
| 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.37-py3-none-any.whl
| Download URL | standardbots-2.20260921.37-py3-none-any.whl |
|---|---|
| Size | 87.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2ba4cd1cb7a38730c33f67bcf580a5d8099d1eda711ea0129b60ee96624835e
|
|
BLAKE2b-256 checksum How to use checksums |
db3d07b7c2ba8e2edc32263c5bfd1ad6e4504ec6cd0e0de730abf4da71a389de
|
| 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.37
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.