The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for ball-simulator 0.0.8
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 | |
|---|---|---|---|---|
| ball_simulator-0.0.8.tar.gz | 876 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ball_simulator-0.0.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.2 kB
Release files / ball_simulator-0.0.8.tar.gz
| Download URL | ball_simulator-0.0.8.tar.gz |
|---|---|
| Size | 876 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2a8f8da0df623886faebe627a7fe0643129aa8ce475534bcea400f1d882e7da
|
|
BLAKE2b-256 checksum How to use checksums |
4fd34b8157cedc4690d759a475eec6e10b82c051dc8c0349f88b27313bd4a7be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / ball_simulator-0.0.8-py3-none-any.whl
| Download URL | ball_simulator-0.0.8-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db39559d2b3cc3b98588062ab1985dd5175d4f43beeea68c375a6657b271f5b3
|
|
BLAKE2b-256 checksum How to use checksums |
41e35534c3ad550e713172937c1b26cdfa9a854e776cc5e1d4a8b8513733d0a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for ball-simulator 0.0.8
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.
