Install
NAME
install - four ways to get the binary, in descending order of how much we trust them
FROM SOURCE
Requires Go 1.24 or newer. The module path is on this domain, not on a forge, so nothing is resolved through a third party:
$go install git.driftpipe.sh/driftpipe/cmd/driftpipe@v0.9.4$driftpipe versiondriftpipe 0.9.4 (go1.24.6, linux/amd64, 2026-09-24)
The build has no cgo and no dependencies outside the standard library apart from a YAML decoder, which is why the resulting binary is around 6 MB and starts in under two milliseconds.
PREBUILT BINARIES
Published at dl.driftpipe.sh alongside each tag. Nine builds per release:
| Platform | File | Size |
|---|---|---|
| linux/amd64 | driftpipe_0.9.4_linux_amd64.tar.gz | 2.8M |
| linux/arm64 | driftpipe_0.9.4_linux_arm64.tar.gz | 2.6M |
| linux/386 | driftpipe_0.9.4_linux_386.tar.gz | 2.7M |
| darwin/amd64 | driftpipe_0.9.4_darwin_amd64.tar.gz | 2.9M |
| darwin/arm64 | driftpipe_0.9.4_darwin_arm64.tar.gz | 2.7M |
| windows/amd64 | driftpipe_0.9.4_windows_amd64.zip | 2.9M |
| windows/arm64 | driftpipe_0.9.4_windows_arm64.zip | 2.7M |
| freebsd/amd64 | driftpipe_0.9.4_freebsd_amd64.tar.gz | 2.8M |
| openbsd/amd64 | driftpipe_0.9.4_openbsd_amd64.tar.gz | 2.8M |
$DP=0.9.4$curl -sSfO "https://dl.driftpipe.sh/v$DP/driftpipe_${DP}_linux_amd64.tar.gz"$curl -sSfO "https://dl.driftpipe.sh/v$DP/SHA256SUMS"$sha256sum --ignore-missing -c SHA256SUMS driftpipe_0.9.4_linux_amd64.tar.gz: OK$tar xzf "driftpipe_${DP}_linux_amd64.tar.gz" driftpipe$install -m 0755 driftpipe /usr/local/bin/driftpipe
The archive contains exactly one file, the binary, with no installer, no post-install script and no shell completion to source. Completions can be generated on demand with driftpipe completion bash if you want them.
OCI IMAGE
Built from the same tag, distroless base, one layer over it, published since 0.9.0:
$docker run --rm -v "$PWD:/w" -w /w \ reg.driftpipe.sh/driftpipe:0.9.4 \ check --schema schema.lock --input events.ndjsondriftpipe 0.9.4 5000 records 30 paths 31msno drift
The entrypoint is the binary itself, so arguments go straight through. Tags are immutable: 0.9.4 will always be that build. There is a latest tag, it moves, and pinning it in a pipeline is a choice you will regret on a Friday.
PACKAGE MANAGERS
None, and none planned. A single static binary with one flag surface does not benefit from nine packaging formats, and maintaining them badly is worse than not having them. If a distribution wants to package it, the build is one go build and we will answer questions.
UNINSTALL
$rm /usr/local/bin/driftpipe$rm -f .driftpipe.yml schema.lock
Nothing else is written anywhere. No state directory, no cache, no configuration under your home directory - the only files driftpipe touches are the ones you name on the command line or in the config file.