The author of this package has not provided a project description
Metadata
Release files for axixalogger 0.0.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 | |
|---|---|---|---|---|
| axixalogger-0.0.0.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axixalogger-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.8 kB
Release files / axixalogger-0.0.0.tar.gz
| Download URL | axixalogger-0.0.0.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
23a09d0ddaf964781591690a2e45a7a6d261115d503b24988afaf25afc2b0fc0
|
|
BLAKE2b-256 checksum How to use checksums |
e5b1e0c8be77573112827191c198039c770e2f34568dac62efff9c4d4b136445
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Release files / axixalogger-0.0.0-py3-none-any.whl
| Download URL | axixalogger-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef1582c118f133a92ec259c57173eee223ae9ce0dd8a02ec1aa4d02591fdaae0
|
|
BLAKE2b-256 checksum How to use checksums |
90b478933e6e27793ee909a5e0c21c42e113f205e700661da205a32861fdd5ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Security for axixalogger 0.0.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.