install

Additional install commands

macOS

Homebrewverified · 100%

brew install xpipe

local Homebrew formula metadata

Linux

Nixverified · 92%

nix profile install nixpkgs#xpipe

nixpkgs package indexes · pkgs/by-name/xp/xpipe/package.nix · source: api.github.com

Windows

Chocolateyverified · 92%

choco install xpipe

Chocolatey community package catalog · xpipe · source: community.chocolatey.org

Scoopverified · 92%

scoop install extras/xpipe

Scoop official bucket manifest trees · bucket/xpipe.json · source: api.github.com

Windows Package Managerverified · 92%

winget install --id xpipe-io.xpipe -e

Windows Package Manager source index · xpipe-io.xpipe · source: cdn.winget.microsoft.com

overview

Package summary

Split input and feed it into the given utility

Project links

Commands and aliases

xpipe

history

Project history and usage

xpipe is Jan Schaumann's small Unix command that splits standard input into chunks and feeds each chunk to a utility. Its README describes it as a conceptual combination of split, tee, and xargs, but with chunks piped to the invoked program rather than passed as command-line arguments.

Project history

The GitHub repository was created on 2020-01-12. The README says xpipe was developed on NetBSD 8.0 and tested on NetBSD 8.0, macOS 12.6, and Fedora 36, matching Schaumann's broader Unix/pkgsrc background.

The project is intentionally narrow: one C utility, a manpage-style README, and examples centered on stream chunking. Its design goal is practical shell composition rather than a new pipeline framework.

Adoption history

xpipe's adoption is modest but real in the Unix-tools niche. It appeals to users who understand xargs but need to send each chunk on standard input, such as feeding PEM certificates one at a time to openssl, creating archive batches, or compressing split log chunks.

The README calls out packaging paths for source installs, Arch AUR, pkgsrc, and macOS users, which suggests the tool spread mainly through small-package ecosystems and personal Unix workflows rather than through a large application stack.

How it is used

xpipe reads stdin, splits by byte count, line count, or a regular-expression pattern, then invokes the chosen utility repeatedly with the chunk connected to that utility's stdin. The -J option can substitute an invocation number into command arguments, making per-chunk output files straightforward.

The most distinctive usage is pattern-delimited input where temporary files would otherwise be annoying. The README's certificate example splits a PEM bundle at END CERTIFICATE lines and feeds each certificate to openssl x509 for inspection.

Why package nerds care

xpipe is the kind of tiny Unix command package nerds like: it fills one gap in the standard toolbox without inventing a new ecosystem. It is easiest to understand as xargs for stdin chunks rather than argv construction.

Its significance is also pedagogical. By naming the space between split, tee, and xargs, xpipe makes a common shell-script pattern explicit and reusable, reducing the need for ad hoc sed/awk loops and temporary-file cleanup.

Timeline

2020-01-12: The jschauma/xpipe repository is created.
2020s: xpipe is documented as developed on NetBSD 8.0 and tested on NetBSD, macOS, and Fedora.
2026: The GitHub repository remains active with a compact C implementation and manpage-oriented README.

Related projects

xargs is the closest standard utility, but it constructs command arguments rather than piping each input chunk to stdin.
split is related because it partitions input, though xpipe avoids forcing intermediate files.
tee is related in the README's conceptual model because xpipe routes input into repeated downstream processes.

Sources

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

narrow executable package without higher-risk signals

Signals

metadata:no-higher-risk-signals

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 13 platform targets.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

Command	Kind	Exposure	Note
`xpipe`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08

manager version2.2

manager updated2026-06-25

local dataok

upstreamnot checked

latest detectednot detected

https://www.netmeister.org/apps/xpipe.html

infoRelease/tag comparison is only available for GitHub repositories.https://www.netmeister.org/apps/xpipe.htmlnone confidence

install metadata

Package metadata

Package key	brew:xpipe
Version	2.2
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/xpipe
Homepage	https://www.netmeister.org/apps/xpipe.html
Repository	https://github.com/jschauma/xpipe
Upstream docs	https://github.com/jschauma/xpipe#readme
License	BSD-2-Clause
Source archive	https://www.netmeister.org/apps/xpipe-2.2.tar.gz
Last updated	2026-06-25T13:38:12+02:00
Pulse	updated
Bottle	available (on arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	xpipe
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

xpipe

nix profile install nixpkgs#xpipe

normalized package name match
Matched by: Xpipe

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/xp/xpipe/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

Chocolatey95%

xpipe

choco install xpipe

normalized package name match
Matched by: Xpipe

Chocolatey community package catalog · community.chocolatey.org · Chocolatey community package catalog: xpipe from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='9.1916','tektoncd-cli'

Scoop95%

extras/xpipe

scoop install extras/xpipe

normalized package name match
Matched by: Xpipe

Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/xpipe.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1

winget95%

xpipe-io.xpipe

winget install --id xpipe-io.xpipe -e

normalized package name match
Matched by: Xpipe

Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: xpipe-io.xpipe from https://cdn.winget.microsoft.com/cache/source.msix

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/xpipe.yml

Used sources

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

Install xpipe with Homebrew, chocolatey, Nix, scoop, winget