1 maintainer
Metadata
1 maintainer
Release files for pro-os-connect-py 0.8.5
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.5.tar.gz | 10.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pro_os_connect_py-0.8.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.6 kB
Release files / pro_os_connect_py-0.8.5.tar.gz
| Download URL | pro_os_connect_py-0.8.5.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1d74523c99b0eaecaa50083c71180f6b23c06b8f8562bc541c184cfa7d2f335
|
|
BLAKE2b-256 checksum How to use checksums |
b89b066225ef327a651ef2e828e6b44f08e3faa9c03759156a4a386550575c2a
|
| 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.5-py3-none-any.whl
| Download URL | pro_os_connect_py-0.8.5-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e0d45b4c31c699e6f5f44cbe54100bf9dc1985d5aa621580af6212ad26e7b2a
|
|
BLAKE2b-256 checksum How to use checksums |
de38d08c8724f0154ed11cb31e0b076143bbfb9a5478ebb0a97cd6914686d60b
|
| 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.5
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.
