Metadata
Release files for jcapi 0.1.5
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 | |
|---|---|---|---|---|
| jcapi-0.1.5.tar.gz | 12.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jcapi-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.0 kB
Release files / jcapi-0.1.5.tar.gz
| Download URL | jcapi-0.1.5.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2d351fa8b323883733380b06757abc92e9d2de49524580d24688dbb355d77c8
|
|
BLAKE2b-256 checksum How to use checksums |
38e7006781ac121c9cc5c7b5c9463c8935bf5ea0826778cd6c1270c901f672dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.50.0 CPython/3.8.5
|
Release files / jcapi-0.1.5-py3-none-any.whl
| Download URL | jcapi-0.1.5-py3-none-any.whl |
|---|---|
| Size | 17.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1197bdef09219213686f1b322278ee7abfb50cc2345c4060ab8f8acb3d7eb58c
|
|
BLAKE2b-256 checksum How to use checksums |
bcfd72cd286ca90774ffcaf9d5b6bfcd43deab7a56b331ebf7907da5556db43a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.50.0 CPython/3.8.5
|
Security for jcapi 0.1.5
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.