The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tadbcmc 0.0.13
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.13.tar.gz | 91.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tadbcmc-0.0.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 192.5 kB
Release files / tadbcmc-0.0.13.tar.gz
| Download URL | tadbcmc-0.0.13.tar.gz |
|---|---|
| Size | 91.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7eb19b9d0fd292267afc538f36ca8260c349a795d0dc877a2f3e972078865a34
|
|
BLAKE2b-256 checksum How to use checksums |
40b1ac51621d8d8c39b29d66ddd8b7a999be09a71e305d4f0508b2ce345a2dca
|
| 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.13-py3-none-any.whl
| Download URL | tadbcmc-0.0.13-py3-none-any.whl |
|---|---|
| Size | 101.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00f7a9501c14e83a7eb1866177d1652acb30db52efb4ec921b54e5fd6738b057
|
|
BLAKE2b-256 checksum How to use checksums |
6d63d7ffb5e30c9c3459e1f22c765a53244293811da2333d7213951a021d442e
|
| 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.13
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.
