1 maintainer
Metadata
1 maintainer
Release files for clinicaltrialsconnect 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 | |
|---|---|---|---|---|
| clinicaltrialsconnect-0.0.0.tar.gz | 5.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| clinicaltrialsconnect-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.9 kB
Release files / clinicaltrialsconnect-0.0.0.tar.gz
| Download URL | clinicaltrialsconnect-0.0.0.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
624b29661332037f5c349586c6a7f8971f5ecacda37f086551d4de64f5ecc147
|
|
BLAKE2b-256 checksum How to use checksums |
2a626a7539d14321e4c326296170f5302e43c32f3b7bed9aac26096cc499ece2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.8.10
|
Release files / clinicaltrialsconnect-0.0.0-py3-none-any.whl
| Download URL | clinicaltrialsconnect-0.0.0-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a7119f944d102aee66594f4b09498a794466a97dd42f15ac29269e73d74aee3
|
|
BLAKE2b-256 checksum How to use checksums |
3506eb7763e0508e3bbea9c8bb0e026503489e6e314f9c074d886c4355d8d5ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.8.10
|
Security for clinicaltrialsconnect 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.
