The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for awpredict 0.1.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 | |
|---|---|---|---|---|
| awpredict-0.1.4.tar.gz | 132.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awpredict-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 243.6 kB
Release files / awpredict-0.1.4.tar.gz
| Download URL | awpredict-0.1.4.tar.gz |
|---|---|
| Size | 132.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f345e818c091063141541f1802b2cb3d900aefe9b74ebd12e53af2f20d8eeefe
|
|
BLAKE2b-256 checksum How to use checksums |
c614009288fdf77114ab05543bceda65327c307a8d04f8cea53977226413d4d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / awpredict-0.1.4-py3-none-any.whl
| Download URL | awpredict-0.1.4-py3-none-any.whl |
|---|---|
| Size | 111.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
abd45bcd8041af2827f418f178179d06059cb34e613d7c25b233c5579e8f5eab
|
|
BLAKE2b-256 checksum How to use checksums |
60f9edbb5a499e7b745d9eda6b77e517b9c1f78ede5c47caf7303addaeb98f32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for awpredict 0.1.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.
