Metadata
Release files for aclib.winlib 1.2.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 | |
|---|---|---|---|---|
| aclib_winlib-1.2.1.tar.gz | 55.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aclib_winlib-1.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 111.0 kB
Release files / aclib_winlib-1.2.1.tar.gz
| Download URL | aclib_winlib-1.2.1.tar.gz |
|---|---|
| Size | 55.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c20b8239c558d6b913f18cc52692f6874885557de1d1ebf873505c7dc3ea343d
|
|
BLAKE2b-256 checksum How to use checksums |
3128220342a40e034522e8e142ab66ae31d7b22af689e75e813f86948bc12397
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.1
|
Release files / aclib_winlib-1.2.1-py3-none-any.whl
| Download URL | aclib_winlib-1.2.1-py3-none-any.whl |
|---|---|
| Size | 55.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bd1a4ae6bfa9bec8a5bb4cfaf18278bd283521238ad785a6cc40991e0b447945
|
|
BLAKE2b-256 checksum How to use checksums |
a2fc5801f501d90cdd158e17e1b57d4d48f4ee3c56745efc5bf0094bdd58eb76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.1
|
Security for aclib.winlib 1.2.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.