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 1.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-1.0.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| game_run-1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.9 kB
Release files / game_run-1.0.tar.gz
| Download URL | game_run-1.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c0f05691668d70b9491fc005ddf9fea853609ef652d6a9c3366a986fe9a7c1cb
|
|
BLAKE2b-256 checksum How to use checksums |
b181b4b75367441b5f9081801a1d9f924aad2e80b7e36a548a1927d3ecb6e7cf
|
| 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-1.0-py3-none-any.whl
| Download URL | game_run-1.0-py3-none-any.whl |
|---|---|
| Size | 3.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
67d626b18fb66cafb34eee0e7b4174b30f0f9cdf6a9d0f35d91030e535f33c31
|
|
BLAKE2b-256 checksum How to use checksums |
90f9f345b2dc9ba93425b474e07854fa46b706c9fca3d1b3520020e75c868fe3
|
| 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 1.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.
