1 maintainer
Metadata
1 maintainer
Release files for izihawa-trident-py 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 | |
|---|---|---|---|---|
| izihawa_trident_py-1.0.0.tar.gz | 1.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| izihawa_trident_py-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.8 kB
Release files / izihawa_trident_py-1.0.0.tar.gz
| Download URL | izihawa_trident_py-1.0.0.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f64fc67380668f9d2eff0d34490cb581a5a0a0bd62ffe7e19da807aed268c95a
|
|
BLAKE2b-256 checksum How to use checksums |
ca3a9a052268ce1007bf2764ac9d4846ee2c37be3c405a65d080cd64aa387fc1
|
| 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_py-1.0.0-py3-none-any.whl
| Download URL | izihawa_trident_py-1.0.0-py3-none-any.whl |
|---|---|
| Size | 2.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
da9ebc4a35892e4c4c81efab6989ddc744ffcbef37b8bd42ca6f1e4a87961840
|
|
BLAKE2b-256 checksum How to use checksums |
308964e9516dfff68dd5a625800d45ff141a863d71a207dfb5c7906e4b842c5d
|
| 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-py 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.
