1 maintainer
Metadata
1 maintainer
Release files for pred-exp-phase1 0.2.1
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 | |
|---|---|---|---|---|
| pred_exp_phase1-0.2.1.tar.gz | 4.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pred_exp_phase1-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.9 kB
Release files / pred_exp_phase1-0.2.1.tar.gz
| Download URL | pred_exp_phase1-0.2.1.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4d95c3a50803cf5d84bb3101450a2933efb2ee67bb3382d6c2970484fb854d6
|
|
BLAKE2b-256 checksum How to use checksums |
19de6065a778ab3d686494da58a5044203af22e826c127045c0712018002974c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.3 Windows/11
|
Release files / pred_exp_phase1-0.2.1-py3-none-any.whl
| Download URL | pred_exp_phase1-0.2.1-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b9119884e59c9fb488b5cb472376a4ce2f5736a25a7933427fb68eff62f5a067
|
|
BLAKE2b-256 checksum How to use checksums |
5212038917145083734e52b385dc2b08606660f353d9135cc962b40b64cab07b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.3 Windows/11
|
Security for pred-exp-phase1 0.2.1
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.
