The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tadbcmc 0.0.15
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.15.tar.gz | 95.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tadbcmc-0.0.15-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 201.2 kB
Release files / tadbcmc-0.0.15.tar.gz
| Download URL | tadbcmc-0.0.15.tar.gz |
|---|---|
| Size | 95.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3d488f87a91fcf8ea0a86294f6c749a81f1aa73145f66912850903ad3b3de4c
|
|
BLAKE2b-256 checksum How to use checksums |
7346672493a9984fbfb8954b844a338ca1891059de48476609d0ae447a916fb6
|
| 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.15-py3-none-any.whl
| Download URL | tadbcmc-0.0.15-py3-none-any.whl |
|---|---|
| Size | 105.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f83022e7305ec74c2e6df0a9e17dd3a6e6b993cc9bbbc24446deacae75ff6369
|
|
BLAKE2b-256 checksum How to use checksums |
3cc6cce2534a6607ce858ef3fcfe10df3338f56f975b006232ffe36332d35295
|
| 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.15
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.
