1 maintainer
Metadata
1 maintainer
Release files for incar-draccus 0.0.0
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 | |
|---|---|---|---|---|
| incar_draccus-0.0.0.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| incar_draccus-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 kB
Release files / incar_draccus-0.0.0.tar.gz
| Download URL | incar_draccus-0.0.0.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff9353f80a357460b679d142825241947da59da81a5396bff49337c00f7f324a
|
|
BLAKE2b-256 checksum How to use checksums |
9481cd00e5c25d4f35e57ee3c76043fb47502a4be4caca67a0467b89bf40533d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.9
|
Release files / incar_draccus-0.0.0-py3-none-any.whl
| Download URL | incar_draccus-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8c304a49dbd2dab8a4cae783697ea8f24995b4fc2f3779228d4c88eded62f5d7
|
|
BLAKE2b-256 checksum How to use checksums |
ce04c92b6f0db8d24010ea9fe8127b0fa6e86c1ab40c79f0f033379a6e41d120
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.9
|
Security for incar-draccus 0.0.0
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.
