The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tadbcmc 0.0.14
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.14.tar.gz | 94.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tadbcmc-0.0.14-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 200.0 kB
Release files / tadbcmc-0.0.14.tar.gz
| Download URL | tadbcmc-0.0.14.tar.gz |
|---|---|
| Size | 94.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
593f5bbee61ce487d62f19a89cdfde8360a3160f9d519f5a336ed55e8cc585d4
|
|
BLAKE2b-256 checksum How to use checksums |
5ee07b0558c5afaab053e8b48ab1dc4b2e6012980c64f8148ae1a7d988204800
|
| 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.14-py3-none-any.whl
| Download URL | tadbcmc-0.0.14-py3-none-any.whl |
|---|---|
| Size | 105.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9de405e059e593d856183d7b8ea8eb3cb203532408a51bd5c8c680e81abdb326
|
|
BLAKE2b-256 checksum How to use checksums |
2feb9d269bb3f85ba1f8a321422d352d2b029ac3f5c046d20d460b2ef24507bf
|
| 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.14
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.
