The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for appoint-logger 2.0.3
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 | |
|---|---|---|---|---|
| appoint_logger-2.0.3.tar.gz | 4.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| appoint_logger-2.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.0 kB
Release files / appoint_logger-2.0.3.tar.gz
| Download URL | appoint_logger-2.0.3.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4672f805edf28847d417bc083846e3140f713c4f7ecabc633b1479a9987aad11
|
|
BLAKE2b-256 checksum How to use checksums |
0dac89ce92bf2b751fc19a8aa87791c891c973fb349e8cc3df56889ff2059451
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.15
|
Release files / appoint_logger-2.0.3-py3-none-any.whl
| Download URL | appoint_logger-2.0.3-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b942dec2eae99aae474fa9e431b919ba7dd937d21e6da3db9000d0a012a102db
|
|
BLAKE2b-256 checksum How to use checksums |
0fecdd537c2b342e0dc932f22f204704320af85768d96990250e326b84647afb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.15
|
Security for appoint-logger 2.0.3
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.
