Metadata
1 maintainer
Release files for deep-consultation 0.1.8
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 | |
|---|---|---|---|---|
| deep_consultation-0.1.8.tar.gz | 4.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deep_consultation-0.1.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.5 kB
Release files / deep_consultation-0.1.8.tar.gz
| Download URL | deep_consultation-0.1.8.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eec783fb26761f4efbf1d11313eb21e181ce098eb14cd1013246c1640f238ca6
|
|
BLAKE2b-256 checksum How to use checksums |
ab519fe1dfda6a5f3bffa71ecf410f7c5b21e862dd75f3cc31ca7a8bc0280b91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / deep_consultation-0.1.8-py3-none-any.whl
| Download URL | deep_consultation-0.1.8-py3-none-any.whl |
|---|---|
| Size | 5.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
19ca782b05b79f577605065e241d35e0b1338238539eb1661069ee8b0fdf1d88
|
|
BLAKE2b-256 checksum How to use checksums |
0753bb69c8ca95421d7fe19aac33d113cb223556f2342521a3f7e0d1c2e5ed23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for deep-consultation 0.1.8
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.
