The author of this package has not provided a project description
Metadata
Release files for fuzzly-users 0.0.3
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-users-0.0.3.tar.gz | 8.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fuzzly_users-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.2 kB
Release files / fuzzly-users-0.0.3.tar.gz
| Download URL | fuzzly-users-0.0.3.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4b187b2e26e8bc6fc133318a03a4f64a1a4987d39e697de9847b21b29fcb214
|
|
BLAKE2b-256 checksum How to use checksums |
c764e344cff85d13069eee187ffe715b6f5e14be6830b146099c8933c55883de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Release files / fuzzly_users-0.0.3-py3-none-any.whl
| Download URL | fuzzly_users-0.0.3-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5505b4b8fa3ed733af12514748512eb0acec7890005e3ac770b990f13b0a1c8
|
|
BLAKE2b-256 checksum How to use checksums |
1cf8e32449e4ac819abae145066d9a5221b159bbcda89f928840700a511f406a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Security for fuzzly-users 0.0.3
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.