The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tadbcmc 0.0.18
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.18.tar.gz | 101.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tadbcmc-0.0.18-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 213.6 kB
Release files / tadbcmc-0.0.18.tar.gz
| Download URL | tadbcmc-0.0.18.tar.gz |
|---|---|
| Size | 101.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02c1cf760958dfa5cd61a816aa4a73a0c0e55839dddff98e66eea8d5c94d8967
|
|
BLAKE2b-256 checksum How to use checksums |
6d84368826b0c9d4cb9b7cdb99438820b138812ce68e7132e790d7da76bcb82e
|
| 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.18-py3-none-any.whl
| Download URL | tadbcmc-0.0.18-py3-none-any.whl |
|---|---|
| Size | 112.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
201e90bd611be189e2dc5e01771d8b0f4b18bbd48117da52d3d21fc098ac49ac
|
|
BLAKE2b-256 checksum How to use checksums |
a881a42a7f5f67f55de34447b3e8e6b291347906ca50ee241b0215cf4ee2379d
|
| 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.18
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.
