Metadata
1 maintainer
Release files for make4db-duckdb 0.1.2
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 | |
|---|---|---|---|---|
| make4db_duckdb-0.1.2.tar.gz | 2.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| make4db_duckdb-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.0 kB
Release files / make4db_duckdb-0.1.2.tar.gz
| Download URL | make4db_duckdb-0.1.2.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a00ab9c0506ddc18327a3997f1d930a1d096ac08727f05036f8497d994cdbbd
|
|
BLAKE2b-256 checksum How to use checksums |
ff98c869d4815758121853336d1be0a4656e348d11b7cee8155272a919c9682b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.10
|
Release files / make4db_duckdb-0.1.2-py3-none-any.whl
| Download URL | make4db_duckdb-0.1.2-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e4e4d4f257121e2c309fa444ba8b7fd4e92d78d046784163d0cfb28e7b065a5b
|
|
BLAKE2b-256 checksum How to use checksums |
fe20cdb4e561fc9cc681ae6da6f82331db5abd4d479bc1c7c07956786186cd95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.10
|
Security for make4db-duckdb 0.1.2
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.
