1 maintainer
Metadata
1 maintainer
Release files for izihawa-trident 1.0.48
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 | |
|---|---|---|---|---|
| izihawa_trident-1.0.48.tar.gz | 1.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| izihawa_trident-1.0.48-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.8 kB
Release files / izihawa_trident-1.0.48.tar.gz
| Download URL | izihawa_trident-1.0.48.tar.gz |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7699529b0ca0cfbeb76ba4db80497525579715e050ee9c56ba08598e457d03af
|
|
BLAKE2b-256 checksum How to use checksums |
1ac376f967bca83ad1ce83e785309dbff0d086b9189729429e2d9739928807d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.6
|
Release files / izihawa_trident-1.0.48-py3-none-any.whl
| Download URL | izihawa_trident-1.0.48-py3-none-any.whl |
|---|---|
| Size | 2.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7342affccc70b7da9c11c0dd86ca2f2bdf70d9bf5537fe73133fd810d6e57b09
|
|
BLAKE2b-256 checksum How to use checksums |
c20237d3d3687fa19f36ac4f016368a5d9aab27f89ef86e028c270e9e33e60ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.6
|
Security for izihawa-trident 1.0.48
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.
