The author of this package has not provided a project description
Metadata
Release files for epp-logs-to-sqlite 2.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 | |
|---|---|---|---|---|
| epp_logs_to_sqlite-2.0.tar.gz | 3.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| epp_logs_to_sqlite-2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.8 kB
Release files / epp_logs_to_sqlite-2.0.tar.gz
| Download URL | epp_logs_to_sqlite-2.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf6db286bf46b8e9fa9e94ccb628e5db860e2bfab367e846f543b22c1b6cc6f0
|
|
BLAKE2b-256 checksum How to use checksums |
c4947ab41ab03492f43ec7e7477f2745c7a97854f1083091be977a348aac0023
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.3
|
Release files / epp_logs_to_sqlite-2.0-py3-none-any.whl
| Download URL | epp_logs_to_sqlite-2.0-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eaa9824d49361168f3571608a87e85647f67be35c363d5ecb2e29c0ed5ddf101
|
|
BLAKE2b-256 checksum How to use checksums |
1577caa0fe4231f313d2a102c21774808d7b7c0f2a20586af4d1813441874dc3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.3
|
Security for epp-logs-to-sqlite 2.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.