1 maintainer
Metadata
1 maintainer
Release files for izihawa-trident-client 1.4.2
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_client-1.4.2.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| izihawa_trident_client-1.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.6 kB
Release files / izihawa_trident_client-1.4.2.tar.gz
| Download URL | izihawa_trident_client-1.4.2.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60ab93616ee63f5f4c212c0a1e44156b72b8cf8009adba2f01359815b0cc88d4
|
|
BLAKE2b-256 checksum How to use checksums |
af3398f2f207f4d9440a817ac79d724096d79c78fd7d081e435c651ddc0e8d41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Release files / izihawa_trident_client-1.4.2-py3-none-any.whl
| Download URL | izihawa_trident_client-1.4.2-py3-none-any.whl |
|---|---|
| Size | 3.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
749624e4c79e49ccbad7e99b2b31587e42c1bd76f6fb068eda1c181827dc431b
|
|
BLAKE2b-256 checksum How to use checksums |
dc02b95de43057db17d018c97462a872ece07af34722c45956fd35a5e33c0bdd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Security for izihawa-trident-client 1.4.2
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.
