The author of this package has not provided a project description
Metadata
Release files for sane-logger 0.0.6
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 | |
|---|---|---|---|---|
| sane_logger-0.0.6.tar.gz | 2.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sane_logger-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.8 kB
Release files / sane_logger-0.0.6.tar.gz
| Download URL | sane_logger-0.0.6.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3a50fd883da2dcab5a134d947ae14d15e71b9134c83a1fc104aa1aa1376a063
|
|
BLAKE2b-256 checksum How to use checksums |
d45e58a45dc4d15c576cf23001036d7434c4903d15ab4985399bcc3417d4390f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.2
|
Release files / sane_logger-0.0.6-py3-none-any.whl
| Download URL | sane_logger-0.0.6-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
74c9a3180431e660d67967b5004e69502314e94e5088c83ab12ffc845d90a16d
|
|
BLAKE2b-256 checksum How to use checksums |
53607e5060daf7ec05ce18f410339beac3facdef7c54bcec156af207fd46a9ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.2
|
Security for sane-logger 0.0.6
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.