Metadata
1 maintainer
Release files for autocontour 0.0.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 | |
|---|---|---|---|---|
| autocontour-0.0.1.tar.gz | 4.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autocontour-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.0 kB
Release files / autocontour-0.0.1.tar.gz
| Download URL | autocontour-0.0.1.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f53456a003919cffe9baf153fc44b646b3cde6e5e7e9f3bb52791c8522345618
|
|
BLAKE2b-256 checksum How to use checksums |
730fb0a658004b5377c1d55cb2c974d4678f6b2d6d6ef5a6d6972609b0bb3ffe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / autocontour-0.0.1-py3-none-any.whl
| Download URL | autocontour-0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fac466359d2b93e08d063b4f7fd7f2a7a838892d98e4ab320cfac4aec5a7914b
|
|
BLAKE2b-256 checksum How to use checksums |
390823d32794a7fe01398e8f4662b0befe7a5ccc0f62d525e5be0b3d459ccd8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for autocontour 0.0.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.
