The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for bibfetch 0.0.3
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 | |
|---|---|---|---|---|
| bibfetch-0.0.3.tar.gz | 3.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bibfetch-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.4 kB
Release files / bibfetch-0.0.3.tar.gz
| Download URL | bibfetch-0.0.3.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
77280bcd616f928b18e2f898747f32f93cdb1f5b9ec4bc752e0d4192e46cbb28
|
|
BLAKE2b-256 checksum How to use checksums |
2061428738de19432848e11efd6f129040240190b90ad8fef0af697f6e34788c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.8
|
Release files / bibfetch-0.0.3-py3-none-any.whl
| Download URL | bibfetch-0.0.3-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
486de6458da7cbf7011b5f6ad7f42dd23951b024ee3ebd4cfcc2ee7fe125e948
|
|
BLAKE2b-256 checksum How to use checksums |
d73d9b02130101af40e56ef8b5146cbd5b1089ae5559042ce2fd160c238571fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.8
|
Security for bibfetch 0.0.3
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.
