The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for optima-robotics 1.0
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 | |
|---|---|---|---|---|
| optima-robotics-1.0.tar.gz | 1.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| optima_robotics-1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.1 kB
Release files / optima-robotics-1.0.tar.gz
| Download URL | optima-robotics-1.0.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
99b8dda396093c04ca993c570e6ad086e3565211247bce78e3116d9cc50f2639
|
|
BLAKE2b-256 checksum How to use checksums |
7900fb078edb4399bfa36d7a6b7a03852bb58f9d07dc705540f8e1879daafa56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.0
|
Release files / optima_robotics-1.0-py3-none-any.whl
| Download URL | optima_robotics-1.0-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a41456663f937d3ce456ac2580d0c1c42d73607faa74fc11e2ae95af4d4f2a17
|
|
BLAKE2b-256 checksum How to use checksums |
aaa01960bb67e39e5348089ed89e9fcbb093eeda4c07bf7ceb579899f6d2aef0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.0
|
Security for optima-robotics 1.0
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.
