1 maintainer
Metadata
1 maintainer
Release files for pubmed-meta-analyzer 0.1
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 | |
|---|---|---|---|---|
| pubmed_meta_analyzer-0.1.tar.gz | 4.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pubmed_meta_analyzer-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.6 kB
Release files / pubmed_meta_analyzer-0.1.tar.gz
| Download URL | pubmed_meta_analyzer-0.1.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05e9ab199e568d188c44d643cc89e07123912e1498a003db49f1c04ae9624226
|
|
BLAKE2b-256 checksum How to use checksums |
de454f1ba90a244e9caab9f5b3f077684eb99b6f2fa57437924d20b798d1fd1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.0
|
Release files / pubmed_meta_analyzer-0.1-py3-none-any.whl
| Download URL | pubmed_meta_analyzer-0.1-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab91c4c74df4a9987a1a956daf6ddf8753d408bf18be8441afa53f896ef25c4f
|
|
BLAKE2b-256 checksum How to use checksums |
ab91882de29a190963eea1d8e983cac884faa211de6fbb328a3ec4dd8854e057
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.0
|
Security for pubmed-meta-analyzer 0.1
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.
