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.2
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.2.tar.gz | 7.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| game_run-4.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.4 kB
Release files / game_run-4.0.2.tar.gz
| Download URL | game_run-4.0.2.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3dcc1e8e9fcb06eaa91e6de228140d914b7d9281c67eefb09b82bcafb9e1f2f1
|
|
BLAKE2b-256 checksum How to use checksums |
18bfab871f03bfd1fa7ca71ef40174f6141b5ffd93550481da7b85d9511eaa0c
|
| 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.2-py3-none-any.whl
| Download URL | game_run-4.0.2-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b4f403605b2180530ed3e0fa52839e0644c087bf8ffdabefc3ebdec112496535
|
|
BLAKE2b-256 checksum How to use checksums |
3ebb2406e905c908146eb1598939295d3978876012eaf2811d6a5ede42f2d1af
|
| 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.2
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.