The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for ctconvert 0.0.2
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 | |
|---|---|---|---|---|
| ctconvert-0.0.2.tar.gz | 975.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ctconvert-0.0.2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 2.0 MB
Release files / ctconvert-0.0.2.tar.gz
| Download URL | ctconvert-0.0.2.tar.gz |
|---|---|
| Size | 975.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f326946850a36534b2fd08556c7735ef1195cb7faea4b8d29bcb674258c6644
|
|
BLAKE2b-256 checksum How to use checksums |
e2645a05e677cbd36dcdbd62b2d312ea8e586feb869568423c37adf5a019c3ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.22.0
|
Release files / ctconvert-0.0.2-py2.py3-none-any.whl
| Download URL | ctconvert-0.0.2-py2.py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
07a9107b35df503e79a91f4de6deb4c3cce4d86aeb5639980f12011506a2241a
|
|
BLAKE2b-256 checksum How to use checksums |
e75d5a2895137292e788cd45687ff5b9509d2dab4c1bca135e3effd050fc8b74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.22.0
|
Security for ctconvert 0.0.2
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.
