1 maintainer
Metadata
1 maintainer
Release files for pro-os-connect-py 0.8.6
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.6.tar.gz | 10.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pro_os_connect_py-0.8.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.6 kB
Release files / pro_os_connect_py-0.8.6.tar.gz
| Download URL | pro_os_connect_py-0.8.6.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7eb7bb6b2d6c751a06fb6241c472432f02fdec6448976f86002517352091bcdf
|
|
BLAKE2b-256 checksum How to use checksums |
2e9a94c24e7d828ff6d3a9c8d17713c2ff80088e5eac1d884c7c07ce7776ef0a
|
| 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.6-py3-none-any.whl
| Download URL | pro_os_connect_py-0.8.6-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ff90359b46b34e73e7d8a472b02b7d95b01d01c47ca1446fe39a8d6ddf9bf847
|
|
BLAKE2b-256 checksum How to use checksums |
b7b0b64f147599308fa5df6cc19a5abb279fdb6a41bd22fe4382f95e45627c76
|
| 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.6
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.
