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 4.0.4
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.4.tar.gz | 9.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| game_run-4.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.3 kB
Release files / game_run-4.0.4.tar.gz
| Download URL | game_run-4.0.4.tar.gz |
|---|---|
| Size | 9.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dabf443aa608dbb745f83495cf34ae4ad2c98e3eb4ed534366bca943cb1633b0
|
|
BLAKE2b-256 checksum How to use checksums |
17099b50732f35ab3181766f238f7ec0d5af373a67fb857d3db48eee01ca1744
|
| 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.4-py3-none-any.whl
| Download URL | game_run-4.0.4-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9daafd2795519b775304890ce3dd95c02539b90988a215e97955f67a3884e58e
|
|
BLAKE2b-256 checksum How to use checksums |
04a271c57c3053dc01c58a0987a3b41fc703bd59f6bb9d9c739abfc93b654bf3
|
| 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.4
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.
