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 2.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 | |
|---|---|---|---|---|
| game_run-2.0.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| game_run-2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.3 kB
Release files / game_run-2.0.tar.gz
| Download URL | game_run-2.0.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9674c0942b3db0a23d824a1e8e5c3b814c518d8f922314be9a776ddf3eee8275
|
|
BLAKE2b-256 checksum How to use checksums |
3c06039f9b9a2f4e4db3c381fdf2e9d298a99963cefff8ea486846ecae279636
|
| 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-2.0-py3-none-any.whl
| Download URL | game_run-2.0-py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bed9b1ebb61c3209b50756b809b4857adc4d15582b5c850b6294924ec03da95b
|
|
BLAKE2b-256 checksum How to use checksums |
a9d49fc24c02038d99c3b7df1ad3039cb982cc951c1bcbcae2069b72faef159b
|
| 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 2.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.
