The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for auxi-core 2.2.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 | |
|---|---|---|---|---|
| auxi_core-2.2.5.tar.gz | 785.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auxi_core-2.2.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 818.4 kB
Release files / auxi_core-2.2.5.tar.gz
| Download URL | auxi_core-2.2.5.tar.gz |
|---|---|
| Size | 785.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b73627f349d8dd04f5295b5fa78d797f547c7aa41f473f4d58d11333babf409
|
|
BLAKE2b-256 checksum How to use checksums |
315bc9d9c1b0c1d37b186fb0672fe91dbbcce56859204d383dd29443c66317c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Release files / auxi_core-2.2.5-py3-none-any.whl
| Download URL | auxi_core-2.2.5-py3-none-any.whl |
|---|---|
| Size | 32.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f76f8b6664d1a8f165039b67e715bbefa51580eaed5eb7e2b9f307eef173fb87
|
|
BLAKE2b-256 checksum How to use checksums |
313ea2868f44ca4684e5d955273734162681bb5c2be73a80ee0b2177ad1103d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Security for auxi-core 2.2.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.
