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.7
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.7.tar.gz | 12.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| game_run-4.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.7 kB
Release files / game_run-4.0.7.tar.gz
| Download URL | game_run-4.0.7.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
011b519e75fb98d64d82f988e494b01490f082cae30fb58c6f28393c586d5f5f
|
|
BLAKE2b-256 checksum How to use checksums |
a4f8a3ebd780ed3c76957147b6a6391c9cad36e174e22fe4f93d442af15a0aeb
|
| 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.7-py3-none-any.whl
| Download URL | game_run-4.0.7-py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
632b9df4e7bed194bbbafaa44d3d5571e0d4077fd33eff2131a0fb99184c8e42
|
|
BLAKE2b-256 checksum How to use checksums |
58e11a2bcb04ff525ea3374b2c3e483ad41ea216a2b9f03454759d5f1b5b13c1
|
| 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.7
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.