1 maintainer
Metadata
1 maintainer
Release files for hysterical-ticket 0.2.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 | |
|---|---|---|---|---|
| hysterical_ticket-0.2.1.tar.gz | 8.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hysterical_ticket-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.0 kB
Release files / hysterical_ticket-0.2.1.tar.gz
| Download URL | hysterical_ticket-0.2.1.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bfee0120fc95cdf1fa3ae79d2674fe59182ee32490229ee91576d546407c96b2
|
|
BLAKE2b-256 checksum How to use checksums |
08726ee1919ba4781b9e31f46632e810c93bd840a76b301986f47c59abbd21f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.17
|
Release files / hysterical_ticket-0.2.1-py3-none-any.whl
| Download URL | hysterical_ticket-0.2.1-py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eece396ad0913f5fb024e7deba494048d634e6b1190f0a6d20bb5805dee1fbff
|
|
BLAKE2b-256 checksum How to use checksums |
98d7fdf9cc76040207697e083fc2cea7d9fcf06e58da8288ac962bfba637624d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.17
|
Security for hysterical-ticket 0.2.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.
