The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for fuzzly-posts 0.2.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 | |
|---|---|---|---|---|
| fuzzly-posts-0.2.6.tar.gz | 12.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fuzzly_posts-0.2.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.9 kB
Release files / fuzzly-posts-0.2.6.tar.gz
| Download URL | fuzzly-posts-0.2.6.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
383270413fa426a7d07768355e075d8f76a545f7042d5dcee524dc37a3155f6b
|
|
BLAKE2b-256 checksum How to use checksums |
c21f6084a324674e19a70e2c45c8ac46a7946804d7f8c83e6754403cc0913d62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / fuzzly_posts-0.2.6-py3-none-any.whl
| Download URL | fuzzly_posts-0.2.6-py3-none-any.whl |
|---|---|
| Size | 14.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
64357c23fd0f1471db1535f62364ee09422fec7f5f2bb64bb19492d6484360b1
|
|
BLAKE2b-256 checksum How to use checksums |
1434c998cc33ecfadb28aa94f92188c5b79f245510422db283e036bb4dcd0f82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for fuzzly-posts 0.2.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.
