1 maintainer
Metadata
1 maintainer
Release files for exp_phase1_a 0.1.2
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 | |
|---|---|---|---|---|
| exp_phase1_a-0.1.2.tar.gz | 4.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| exp_phase1_a-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.8 kB
Release files / exp_phase1_a-0.1.2.tar.gz
| Download URL | exp_phase1_a-0.1.2.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a0f1d7964fd19c3a746f0ef4b4c94fefd0dddf68158acd1a697759f3dcf99882
|
|
BLAKE2b-256 checksum How to use checksums |
893c8f7055598765d5491474fb9f283bd1360b9d9f4f655ed85c600eb51c84fb
|
| 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 / exp_phase1_a-0.1.2-py3-none-any.whl
| Download URL | exp_phase1_a-0.1.2-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a2cee2239285ce19b0a5bfdc53db6212af47de450c4b90c85f797a58c1a70fe
|
|
BLAKE2b-256 checksum How to use checksums |
e75aa777ef7955ff52e09612161c17669735a0fa89637ce1c7eaa13774850209
|
| 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 exp_phase1_a 0.1.2
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.
