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.5
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.5.tar.gz | 9.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| game_run-4.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.3 kB
Release files / game_run-4.0.5.tar.gz
| Download URL | game_run-4.0.5.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
39610c2acefaabdb70c48dd1e069852419493e1c9657573b0b2060d8d1f44e51
|
|
BLAKE2b-256 checksum How to use checksums |
0a1f58c40251dd424adb52456ab23ff168413223b656994438ede31578a3bc6e
|
| 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.5-py3-none-any.whl
| Download URL | game_run-4.0.5-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be3de5763d24752a5f61aeb8cfd3aa6bd6f00f19649c7358ea4673a9e3824169
|
|
BLAKE2b-256 checksum How to use checksums |
be8a797c2d3a51451012b945b3e812f88ad67320d68512827d410c9dec2933a4
|
| 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.5
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.
