The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tadbcmc 0.0.16
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.16.tar.gz | 95.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tadbcmc-0.0.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 201.5 kB
Release files / tadbcmc-0.0.16.tar.gz
| Download URL | tadbcmc-0.0.16.tar.gz |
|---|---|
| Size | 95.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6127f5821d09ea752c5f99bbff2fcb926a4cd2fc223f655d60b1b90e75144089
|
|
BLAKE2b-256 checksum How to use checksums |
958598023e625ee2d809b6d21b42ad5323ef91dc99d2df7ec4ba1a1531469933
|
| 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.16-py3-none-any.whl
| Download URL | tadbcmc-0.0.16-py3-none-any.whl |
|---|---|
| Size | 105.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f3327ad49d7fba64fe7946a957c83d183956135006fe45ed25865b692e969ce8
|
|
BLAKE2b-256 checksum How to use checksums |
3207f955c9f11d4afa88fbede220420135a44f5fbb4e4847d71ac9e5a95fc50a
|
| 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.16
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.
