The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for fuad-namer 1.0.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 | |
|---|---|---|---|---|
| fuad_namer-1.0.0.tar.gz | 1.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fuad_namer-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.3 kB
Release files / fuad_namer-1.0.0.tar.gz
| Download URL | fuad_namer-1.0.0.tar.gz |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ac008eedd1b5a1db795d8ba6b0ce875ccee3a800a69450c425c1840cdd8a2fea
|
|
BLAKE2b-256 checksum How to use checksums |
172e8ea704e98aa9c8af7aba0d0b253f01e8b478744081f5c6074e1cf25432fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.5
|
Release files / fuad_namer-1.0.0-py3-none-any.whl
| Download URL | fuad_namer-1.0.0-py3-none-any.whl |
|---|---|
| Size | 1.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a4e7b8417b5cc570580c6e1f5cdf2d7d36231fae14527f5fa4469b4ff118a99
|
|
BLAKE2b-256 checksum How to use checksums |
ff78a3f30a80c2f3926b89bce9a13e07472099d0564c4c15f7654147348cf5f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.5
|
Security for fuad-namer 1.0.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.
