The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for fuzzly-configs 0.0.4
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-configs-0.0.4.tar.gz | 8.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fuzzly_configs-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.3 kB
Release files / fuzzly-configs-0.0.4.tar.gz
| Download URL | fuzzly-configs-0.0.4.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ec7eeaadeb5cac6ee8202c13aff556c68fd851c50c6c6b517a7a506306e6caf
|
|
BLAKE2b-256 checksum How to use checksums |
5a5a3bf555eec04e28897d5fc83569832d62afeaa8e5a22c63704a786fc2c494
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / fuzzly_configs-0.0.4-py3-none-any.whl
| Download URL | fuzzly_configs-0.0.4-py3-none-any.whl |
|---|---|
| Size | 9.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc30048be4f076d10643933d8f694968a619a8b3b64fcb81cec3d34fc8f3ad5c
|
|
BLAKE2b-256 checksum How to use checksums |
976d286c2f2fceedac7d711e90b8ac6a35827c3246f13a085e58f19b126e9a20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for fuzzly-configs 0.0.4
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.
