Metadata
Release files for readwise-to-datasette 0.2.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 | |
|---|---|---|---|---|
| readwise_to_datasette-0.2.0.tar.gz | 1.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| readwise_to_datasette-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.5 kB
Release files / readwise_to_datasette-0.2.0.tar.gz
| Download URL | readwise_to_datasette-0.2.0.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e62cb78edaf730dbc5373be93a29c32e9f86bf00bfd2abc10a5128f7d45363c
|
|
BLAKE2b-256 checksum How to use checksums |
efc4787d29b8d292cab85be30a79e10544d47c4f3e208080eee23041dd30822e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.12.1 Linux/6.2.0-1018-azure
|
Release files / readwise_to_datasette-0.2.0-py3-none-any.whl
| Download URL | readwise_to_datasette-0.2.0-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
87dfb0630878aa44043d217859479f6e4bcf8e0278ecd3b0f704e20efe5e4799
|
|
BLAKE2b-256 checksum How to use checksums |
77511a9c5b693021f5be3e7ef259891ecb5c9ca195f018fb109d8f758707eb58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.7.1 CPython/3.12.1 Linux/6.2.0-1018-azure
|
Security for readwise-to-datasette 0.2.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.