1 maintainer
Metadata
1 maintainer
Release files for pro-os-connect-py 0.8.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 | |
|---|---|---|---|---|
| pro_os_connect_py-0.8.0.tar.gz | 10.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pro_os_connect_py-0.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.4 kB
Release files / pro_os_connect_py-0.8.0.tar.gz
| Download URL | pro_os_connect_py-0.8.0.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cbdc0882e239edd51dcf01d6469d6435e93fcd69d425fc9acab05b31535a47f5
|
|
BLAKE2b-256 checksum How to use checksums |
e08a05ce603a9590a34865c4553afd1b6c3f8911bd94fa225e9ef5b156577491
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Release files / pro_os_connect_py-0.8.0-py3-none-any.whl
| Download URL | pro_os_connect_py-0.8.0-py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ffd352bd798feacdd4cefa23e6303595b414b64058cc2eef126b6dca03d2a0e
|
|
BLAKE2b-256 checksum How to use checksums |
68099de6e3b8b924c308b1217d4ed0d69e78848efc9ef5981136a1878f06b307
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for pro-os-connect-py 0.8.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.
