1 maintainer
Metadata
1 maintainer
Release files for ignite-rich-logger 1.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 | |
|---|---|---|---|---|
| ignite_rich_logger-1.0.0.tar.gz | 6.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ignite_rich_logger-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.8 kB
Release files / ignite_rich_logger-1.0.0.tar.gz
| Download URL | ignite_rich_logger-1.0.0.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0176d28bc353a416c8caf45f4c58b6a3ee27da75330c472aea659caca2479912
|
|
BLAKE2b-256 checksum How to use checksums |
b368d94a8d78734a2a05bf47348be12d2ca29e3260f773c51241a003cee2f6e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / ignite_rich_logger-1.0.0-py3-none-any.whl
| Download URL | ignite_rich_logger-1.0.0-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
737fd9b13f97ddafd04ef4514c0be3b5df6ac956cd3bdf486c597354bbfea88e
|
|
BLAKE2b-256 checksum How to use checksums |
048061fe126c59b36174f1b8fb436d2d0f881405f5b94462988bd20ead16a7c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for ignite-rich-logger 1.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.
