The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for tadbcmc 0.0.17
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.17.tar.gz | 98.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tadbcmc-0.0.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 206.8 kB
Release files / tadbcmc-0.0.17.tar.gz
| Download URL | tadbcmc-0.0.17.tar.gz |
|---|---|
| Size | 98.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82019f18316ce0b8009aa6efb1e4b15489aa00cf6543ea8225dfc1539e83e566
|
|
BLAKE2b-256 checksum How to use checksums |
0cd479b3f5125ae22c427b34405604315cd6cbb4b041e79682fefc3137d2b064
|
| 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.17-py3-none-any.whl
| Download URL | tadbcmc-0.0.17-py3-none-any.whl |
|---|---|
| Size | 108.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f5f3072a1143d3dd30333177cbb1c28600452580839a3b6711b1504fed925b6
|
|
BLAKE2b-256 checksum How to use checksums |
b946bd4a3a8d80eb65857655c5fcb2a581bf80489fd62b3052430d356814f03a
|
| 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.17
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.
