Release files for dicom-sequence-classifier 1.0.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 | |
|---|---|---|---|---|
| dicom_sequence_classifier-1.0.5.tar.gz | 5.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dicom_sequence_classifier-1.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.5 kB
Release files / dicom_sequence_classifier-1.0.5.tar.gz
| Download URL | dicom_sequence_classifier-1.0.5.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a70f47000b32d6a11d3c826f51e91a6c1607d9783d3bc0970a57ab75d661882f
|
|
BLAKE2b-256 checksum How to use checksums |
9260ed3b80ca78cfd1307a15530a3343db31d0ffbc1ec29cbbc12b056dbffb61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.7
|
Release files / dicom_sequence_classifier-1.0.5-py3-none-any.whl
| Download URL | dicom_sequence_classifier-1.0.5-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a146e12bac88b9b9f2480ff72f046ee94e75df93bb9f0a830a9abd42cecf8bcf
|
|
BLAKE2b-256 checksum How to use checksums |
86d65abc933892466d17eb76d5521c1349cf05265351bbb62762b0e9b6e1bc92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.7
|
Security for dicom-sequence-classifier 1.0.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.
