only view the source code if you want to see how the games code was generated.
MIT licence
1 maintainer
Metadata
1 maintainer
Release files for game-run 4.0.6
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 | |
|---|---|---|---|---|
| game_run-4.0.6.tar.gz | 9.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| game_run-4.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.3 kB
Release files / game_run-4.0.6.tar.gz
| Download URL | game_run-4.0.6.tar.gz |
|---|---|
| Size | 9.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71e0d8d252be5ca1b7651ca65a7062b585215671e7061470442b204fe3c094c2
|
|
BLAKE2b-256 checksum How to use checksums |
a27ef1c5c0b71f9bb8aeff8939c4b227c1c79af89302ebfa8e1be2e98b0ce9f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.5
|
Release files / game_run-4.0.6-py3-none-any.whl
| Download URL | game_run-4.0.6-py3-none-any.whl |
|---|---|
| Size | 11.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
611a23bdc8d8c1c71159d149e599e2c894209e1e42dc67a6ba86ac9e4778823c
|
|
BLAKE2b-256 checksum How to use checksums |
0889496a535e8223f2423592a58a611adb88559f15d32d6c384413ae43466777
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.5
|
Security for game-run 4.0.6
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.
