The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tadbcmc 0.0.19
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 | |
|---|---|---|---|---|
| tadbcmc-0.0.19.tar.gz | 104.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tadbcmc-0.0.19-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 220.5 kB
Release files / tadbcmc-0.0.19.tar.gz
| Download URL | tadbcmc-0.0.19.tar.gz |
|---|---|
| Size | 104.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de092c6261f9c41b0823ac636ad2e8ad4a01efc201b2a8d2b27252b089cd1f96
|
|
BLAKE2b-256 checksum How to use checksums |
91549c510b9a199a2577468821629792d74f5daff3db1eb33daae12e52077d47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Release files / tadbcmc-0.0.19-py3-none-any.whl
| Download URL | tadbcmc-0.0.19-py3-none-any.whl |
|---|---|
| Size | 116.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f049aa231f9f763a8d76a4de4ef6188f3b361bd5cd69acf3510d86551f391a55
|
|
BLAKE2b-256 checksum How to use checksums |
da93bce2385ebc3e66d43c6d0f6e932638b3e510e937b2303623a1134e26b2f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Security for tadbcmc 0.0.19
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.
