This release is a pre-release and may not be stable for production use.
haybarn-cli on PyPI
Run Haybarn — an independent derived distribution of DuckDB — directly from PyPI:
uvx haybarn-cli -c "SELECT 'powered by DuckDB' AS haybarn;"
# or
pipx run haybarn-cli -c "SELECT 'powered by DuckDB' AS haybarn;"
What this is
haybarn-cli is a binary-distribution package. Each PyPI wheel embeds
the pre-built haybarn binary for one platform, tagged so pip / uv
auto-select the correct one:
manylinux_2_28_x86_64— glibc-based Linux on x86_64manylinux_2_28_aarch64— glibc-based Linux on aarch64musllinux_1_2_x86_64— Alpine / musl Linux on x86_64musllinux_1_2_aarch64— Alpine / musl Linux on aarch64macosx_11_0_x86_64— macOS 11+ on Intelmacosx_11_0_arm64— macOS 11+ on Apple Siliconwin_amd64— 64-bit Windows
The Python shim (haybarn_cli:main) os.execvs into the bundled
binary, so signals and exit codes propagate naturally.
Versions
uvx haybarn-cli— latest stable.uvx haybarn-cli@1.5.2rc7— pin to a specific release candidate. (PEP 440 normalizes1.5.2-rc7→1.5.2rc7.)
Related
haybarn(npm) — same binary, run vianpx haybarn.haybarn-python(PyPI, future) — Python library with native bindings (import haybarn as duckdb). Different package; this one is just the CLI.
Trademark
Haybarn is an independent derived distribution of DuckDB published by Query Farm LLC. Not affiliated with or endorsed by the DuckDB Foundation. DuckDB is a trademark of the DuckDB Foundation.
1 maintainer
Metadata
1 maintainer
Release files for haybarn-cli 1.5.6rc1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| haybarn_cli-1.5.6rc1-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| haybarn_cli-1.5.6rc1-py3-none-musllinux_1_2_x86_64.whl | Python 3 | none | Linux musl 1.2+ x86-64 | Details |
| haybarn_cli-1.5.6rc1-py3-none-musllinux_1_2_aarch64.whl | Python 3 | none | Linux musl 1.2+ ARM64 | Details |
| haybarn_cli-1.5.6rc1-py3-none-manylinux_2_28_x86_64.whl | Python 3 | none | Linux glibc 2.28+ x86-64 | Details |
| haybarn_cli-1.5.6rc1-py3-none-manylinux_2_28_aarch64.whl | Python 3 | none | Linux glibc 2.28+ ARM64 | Details |
| haybarn_cli-1.5.6rc1-py3-none-macosx_11_0_x86_64.whl | Python 3 | none | macOS 11.0+ x86-64 | Details |
| haybarn_cli-1.5.6rc1-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
Total release size: 133.9 MB
Release files / haybarn_cli-1.5.6rc1-py3-none-win_amd64.whl
| Download URL | haybarn_cli-1.5.6rc1-py3-none-win_amd64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
e28b6cdfe1d549437ee463fd0a70a570254b48e5534d34947b0c0ef6fbc66b1c
|
|
BLAKE2b-256 checksum How to use checksums |
2c001896d031dade4b66bf9b394e430632d556675b61af079f76a0f9b9738435
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / haybarn_cli-1.5.6rc1-py3-none-musllinux_1_2_x86_64.whl
| Download URL | haybarn_cli-1.5.6rc1-py3-none-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 23.4 MB |
| Tags | Linux musl 1.2+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
d67c8e66d8b4773950108f5e717448b22a7dfa3b30e541763c5e64cb39117951
|
|
BLAKE2b-256 checksum How to use checksums |
0d809a1cd38f4b194c0f8f251665311fea7c63c88b0dc6b0986366ff960d1157
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / haybarn_cli-1.5.6rc1-py3-none-musllinux_1_2_aarch64.whl
| Download URL | haybarn_cli-1.5.6rc1-py3-none-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 21.8 MB |
| Tags | Linux musl 1.2+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
ad6d3a9cc65a9165e62812eac7a22754f41de732bcd8fda0f40c60a2ce130926
|
|
BLAKE2b-256 checksum How to use checksums |
0940c4d24b6e0ed078891895a19e59efe800ab477ffdf153809ab06d37100023
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / haybarn_cli-1.5.6rc1-py3-none-manylinux_2_28_x86_64.whl
| Download URL | haybarn_cli-1.5.6rc1-py3-none-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 22.2 MB |
| Tags | Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
808308446e5d543d223549857711611a81bfa4b8dd7bbcfe5064ba9e36aa99f7
|
|
BLAKE2b-256 checksum How to use checksums |
fc09f3e574fa8181f1e389073ac4b68dc3a682e8addb28f0649fce237bb70d54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / haybarn_cli-1.5.6rc1-py3-none-manylinux_2_28_aarch64.whl
| Download URL | haybarn_cli-1.5.6rc1-py3-none-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 20.2 MB |
| Tags | Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
e25f22967fbe5d6917f901283c031d89782757586bf26144764bdf5fb985f0d9
|
|
BLAKE2b-256 checksum How to use checksums |
eae5089a16c6bfdf07ec60ff0111e5dcd819595989c99cdeb19d8ce249882fd4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / haybarn_cli-1.5.6rc1-py3-none-macosx_11_0_x86_64.whl
| Download URL | haybarn_cli-1.5.6rc1-py3-none-macosx_11_0_x86_64.whl |
|---|---|
| Size | 19.0 MB |
| Tags | Python 3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
2c34268d902bf27ad10dd4057026535a6e08e7e07055894d1602a5a37078acd0
|
|
BLAKE2b-256 checksum How to use checksums |
753327dd1b8bed6eb762f2b529b075120d8d80c2d639ae3f62ab6379444579fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / haybarn_cli-1.5.6rc1-py3-none-macosx_11_0_arm64.whl
| Download URL | haybarn_cli-1.5.6rc1-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 17.2 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
049655de2453b8f699b921b36204f82274f2216ae98a45717609a6ce9c532854
|
|
BLAKE2b-256 checksum How to use checksums |
55028820029df96bef49ea281240e8cfea8c89a5709d02d752921073bc60b8ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logSecurity for haybarn-cli 1.5.6rc1
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.
Full provenance
All 7 files in this release have been uploaded with provenance metadata.
Attestation for haybarn_cli-1.5.6rc1-py3-none-win_amd64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
