only view the source code if you want to see how the games code was generated.
MIT licence
Metadata
Release files for game-run 4.0.3
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.3.tar.gz | 8.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| game_run-4.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.4 kB
Release files / game_run-4.0.3.tar.gz
| Download URL | game_run-4.0.3.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
142ad1e47d771dcaa288cbea51122a05f9f762d17bc2475e1e625100457770a6
|
|
BLAKE2b-256 checksum How to use checksums |
a828195bdedabd70cda9607968537ee06b484638ab3964c308b7d618e3979470
|
| 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.3-py3-none-any.whl
| Download URL | game_run-4.0.3-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3bf8d6b39e0c900595d757f92faef9aa9b784e77ead7c087d98b2875991f458a
|
|
BLAKE2b-256 checksum How to use checksums |
532055bdd844ea494c1dc6c0266687a6add70cef3f765ef6ab7f4b5e7afe8aab
|
| 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.3
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.