this is a very very long description created by iqbal
1 maintainer
Metadata
1 maintainer
Release files for iqsylani46214 0.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 | |
|---|---|---|---|---|
| iqsylani46214-0.1.tar.gz | 1.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iqsylani46214-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 kB
Release files / iqsylani46214-0.1.tar.gz
| Download URL | iqsylani46214-0.1.tar.gz |
|---|---|
| Size | 1.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b77345cd542d72e03927761364f6331bfa43f9fcd833b082d5c4cee3d34ab950
|
|
BLAKE2b-256 checksum How to use checksums |
2ca88c5ba406e4d47ed3ba0b00ec28ec040ac00edcd8b16d2c17cf5fabeac757
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Release files / iqsylani46214-0.1-py3-none-any.whl
| Download URL | iqsylani46214-0.1-py3-none-any.whl |
|---|---|
| Size | 1.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5c6f3977ff9db7fc9a1e51ebe99d0f61ad2942e51672e7cee84f30dc3cd7efd
|
|
BLAKE2b-256 checksum How to use checksums |
5c56433df52cce3f38db6ebaa787270a4beb3c7e5361f2df77a0c42212b00b49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Security for iqsylani46214 0.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.
