The author of this package has not provided a project description
Metadata
Release files for siepic-contradc 0.1.5
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 | |
|---|---|---|---|---|
| siepic_contradc-0.1.5.tar.gz | 205.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| siepic_contradc-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 415.8 kB
Release files / siepic_contradc-0.1.5.tar.gz
| Download URL | siepic_contradc-0.1.5.tar.gz |
|---|---|
| Size | 205.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a3d3bc17081e5b5d33af7069539332e967bedfe078b9b01bd92510fda8c72519
|
|
BLAKE2b-256 checksum How to use checksums |
062236e2fd9f8f08f1249041ddcd44fa48d09690ddbff443cddf20e5307e2198
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Release files / siepic_contradc-0.1.5-py3-none-any.whl
| Download URL | siepic_contradc-0.1.5-py3-none-any.whl |
|---|---|
| Size | 210.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2b524a7217e738bc7344e097906157d866cad69c4c00f640bb7bb0396b68752
|
|
BLAKE2b-256 checksum How to use checksums |
a60e67e52deeab771bf4eb9f4dacaba70909bc43ac175d4f9656494f65fc8315
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Security for siepic-contradc 0.1.5
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.