The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mdcci 2.12.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 | |
|---|---|---|---|---|
| mdcci-2.12.0.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mdcci-2.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.6 kB
Release files / mdcci-2.12.0.tar.gz
| Download URL | mdcci-2.12.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28a067bb2184bce1ac453c12f75b554dd37be401bd2e9b5ed4a47e925ad0b599
|
|
BLAKE2b-256 checksum How to use checksums |
df55525a39f9d1d75020c28df881e6a742bec2c971ae0d5db20e2937d1e0cfdd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / mdcci-2.12.0-py3-none-any.whl
| Download URL | mdcci-2.12.0-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa1d8e0b4838abe055397061a106210c80c73850dad2e33137ad45e55a06a104
|
|
BLAKE2b-256 checksum How to use checksums |
8da3222c53a58868825a3552cf1ccd00366aa26ba359aec568507f92f84f21ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for mdcci 2.12.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.
