The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for LogFusion 0.1.1
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 | |
|---|---|---|---|---|
| logfusion-0.1.1.tar.gz | 5.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| LogFusion-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.2 kB
Release files / logfusion-0.1.1.tar.gz
| Download URL | logfusion-0.1.1.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
615924dd94a255dcaaee84ecc9d26285e7d4880ffed2699505e0fbc40544436f
|
|
BLAKE2b-256 checksum How to use checksums |
da5fb452fcb580ff5068f3f23a0a551a3af058b9293559927f0c5698694a6174
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.2
|
Release files / LogFusion-0.1.1-py3-none-any.whl
| Download URL | LogFusion-0.1.1-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c45949943846514ff9afc51a103fae6bacd6533f7ad7c29c6119216f891d8465
|
|
BLAKE2b-256 checksum How to use checksums |
6c2ca68bea4e9669fc67d8e4547e7e46e2dba66a7c6dfd4a14027c7b472a5bb2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.11.2
|
Security for LogFusion 0.1.1
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.
