1 maintainer
Metadata
1 maintainer
Release files for pro-os-connect-py 0.9.1
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.9.1.tar.gz | 11.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pro_os_connect_py-0.9.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.9 kB
Release files / pro_os_connect_py-0.9.1.tar.gz
| Download URL | pro_os_connect_py-0.9.1.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2be93292c357fe1c77e6566c448e4182ef6293946ecbcdeb2703e97f479fda3
|
|
BLAKE2b-256 checksum How to use checksums |
c4b3b0dbf12cc40db53c38d44a236287db0716fd0edd96af5fd926f82b42c972
|
| 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.9.1-py3-none-any.whl
| Download URL | pro_os_connect_py-0.9.1-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9ca2c467fb242893a23856a8abe372de6d6ffd98fa4cf60f6bcd7c29f838ce5
|
|
BLAKE2b-256 checksum How to use checksums |
9bbb43e5170b5b0fccd4d6c0b845d8ebd25523d6689fea564232a9a19866b317
|
| 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.9.1
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.
