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 3.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-3.0.tar.gz | 5.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| game_run-3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.4 kB
Release files / game_run-3.0.tar.gz
| Download URL | game_run-3.0.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44b80a142e514bffc2ae7b4f50994034b1c40b94c9349100a3914a0ee861a46e
|
|
BLAKE2b-256 checksum How to use checksums |
25933130481a8389d4299165d0a5b115eaa40a1051ed76b14286d1dedfdddd8f
|
| 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-3.0-py3-none-any.whl
| Download URL | game_run-3.0-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e7c47a9df048e11791fb0b0fdc420975d49bb0d6b2eebb4b25ab8634133b25fb
|
|
BLAKE2b-256 checksum How to use checksums |
097251597af34aa4e0541b31c9ae0b9dccab070f3ce79c3ca0ddb1f02efe6ec2
|
| 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 3.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.
