Metadata
Release files for omic 0.0.13
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 | |
|---|---|---|---|---|
| omic-0.0.13.tar.gz | 13.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| omic-0.0.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.0 kB
Release files / omic-0.0.13.tar.gz
| Download URL | omic-0.0.13.tar.gz |
|---|---|
| Size | 13.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eeff00c43277e3299c9cc8813f0cf3bbd7e6ffc8affe04bc5ad3325cc5e7a515
|
|
BLAKE2b-256 checksum How to use checksums |
b59e3afbf89a588d3c5c64354fbc64b4cb2882099936923a72d5926ed0b4b636
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.8.0 tqdm/4.54.1 CPython/3.8.5
|
Release files / omic-0.0.13-py3-none-any.whl
| Download URL | omic-0.0.13-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c0265c1193e03e65ce5d3435189b9e2c0ada7e0d56a4997a6a6808770cdea6f4
|
|
BLAKE2b-256 checksum How to use checksums |
29be80faa8b79c093f281f54fae82fde4155f8f820b3181a3db0f253de63750f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.8.0 tqdm/4.54.1 CPython/3.8.5
|
Security for omic 0.0.13
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.