The author of this package has not provided a project description
Metadata
Release files for baseball-predictor 1.0.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 | |
|---|---|---|---|---|
| baseball_predictor-1.0.0.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| baseball_predictor-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.9 kB
Release files / baseball_predictor-1.0.0.tar.gz
| Download URL | baseball_predictor-1.0.0.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db473a19fe9d6c691ebfff629cca5e5429a3c8900996663e51673dc4c8bb7d4f
|
|
BLAKE2b-256 checksum How to use checksums |
5f1aef6eab14c124b7bc753a3e43b5e7353d05313c945fde0291411a9df4f43e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.11.6
|
Release files / baseball_predictor-1.0.0-py3-none-any.whl
| Download URL | baseball_predictor-1.0.0-py3-none-any.whl |
|---|---|
| Size | 1.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a969db398d263532eb80d9a492fc4c631b94b2c84f04bb0e98ef39578b7f348
|
|
BLAKE2b-256 checksum How to use checksums |
ccc9c127cce88f81046d22611265d854cfcfa48759f30cfe948872a7b72758c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.11.6
|
Security for baseball-predictor 1.0.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.