1 maintainer
Metadata
1 maintainer
Release files for pro-os-connect-py 0.9.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.9.0.tar.gz | 11.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pro_os_connect_py-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.9 kB
Release files / pro_os_connect_py-0.9.0.tar.gz
| Download URL | pro_os_connect_py-0.9.0.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10907b0b17e5b3520536975b75177c06d9cbf8b391cc43e96ce6d6cec9298a50
|
|
BLAKE2b-256 checksum How to use checksums |
ee2cadf2f092c572acb19582b7ead1edcae8c13f2feb480d8946d8d32722447d
|
| 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.0-py3-none-any.whl
| Download URL | pro_os_connect_py-0.9.0-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d5afc6aeb668ecba9b7dc3d421c8c020f688ed974c2a15ade59635b5f1dddfa
|
|
BLAKE2b-256 checksum How to use checksums |
527b913b7e177feacaf261752735628a670de2e2e016744c89383ab8f33765f1
|
| 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.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.
