1 maintainer
Metadata
1 maintainer
Release files for ctconnect-ineelhere 0.0.0
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 | |
|---|---|---|---|---|
| ctconnect_ineelhere-0.0.0.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ctconnect_ineelhere-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.2 kB
Release files / ctconnect_ineelhere-0.0.0.tar.gz
| Download URL | ctconnect_ineelhere-0.0.0.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1159f423a3884af4a9581eee59498e744dbc57929685b37c9109ad98508823a
|
|
BLAKE2b-256 checksum How to use checksums |
772f6438fa56f4267e2bace74777b82842a8717976c7d596c9c4477dbf27ab53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.8.10
|
Release files / ctconnect_ineelhere-0.0.0-py3-none-any.whl
| Download URL | ctconnect_ineelhere-0.0.0-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de808d3d36ef62eaed686ff1940ca1df9ef2ae6301a82937e6d12d4fce4a3f72
|
|
BLAKE2b-256 checksum How to use checksums |
5eaf38f758a0883183c832b4b19134a018e9beeb0781fa3d920d1a16afcdbbf6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.8.10
|
Security for ctconnect-ineelhere 0.0.0
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.
