Pipesmith
The Pipesmith symbol: a chrome pipe in the shape of the letter P with bits inside

Pipesmith

In development. Version 0.1.0 of Pipesmith Registry is out.

Self-hosted tools for the path from source to release. Pipesmith Registry is the artifact repository at the end of that path, for Maven, npm, Docker and raw files. Pipesmith CI builds and checks the code on the way there. Pipesmith Registry is open source.

Download 0.1.0See the registrySource on GitHub

Pipeline

One pipeline runs from source to release. Each product is a station on it, and the registry is the tank at its end.

  1. Start

    Source

    The pipeline starts at your repository, with a push.

  2. The frame

    Pipesmith Suite

    The suite is planned as one orchestration that starts the containers of the two stations below together.

    Planned

  3. Station 1

    Pipesmith CI

    Pipesmith CI is a pipeline kit. A project pulls it in and gets a default configuration with it.

    In development

    More on Pipesmith CI

  4. Station 2, the tank

    Pipesmith Registry

    An artifact repository manager for Maven, npm, Docker and raw files.

    In development

    More on Pipesmith Registry

Registry

Pipesmith Registry serves Maven and Gradle builds, npm installs, Docker pulls and raw file downloads.

The pictures show screens of the administration interface. They are filled with sample data and also show controls for changes, which the server does not make yet.

The tree of the example repository releases with the file auth-client-2.1.0.jar selected and its details shown. Light theme. The tree of the example repository releases with the file auth-client-2.1.0.jar selected and its details shown. Dark theme.
Browse Sample data The folder tree of a repository beside the detail of one file with its checksums and Maven coordinates. Open in full sizeOpen in full size
Pipesmith Registry overview with cards for 13 repositories, 4 formats and 242,672 files served, a table of four blob stores with one unavailable, and the latest tasks with one failed. Light theme. Pipesmith Registry overview with cards for 13 repositories, 4 formats and 242,672 files served, a table of four blob stores with one unavailable, and the latest tasks with one failed. Dark theme.
Overview Sample data The overview shows repositories, formats, files served, the blob stores and the tasks that need attention. Open in full sizeOpen in full size
A table of 13 example repositories with type, format, blob store, state and address. Light theme. A table of 13 example repositories with type, format, blob store, state and address. Dark theme.
Repositories Sample data Hosted, proxy and group repositories for Maven, npm, Docker and raw files in one list. Open in full sizeOpen in full size

CI

Pipesmith CI runs a project through eight stages. One report job merges the results and applies the gate.

The two report pictures show demo runs with sample data. The architecture drawing is made from the configuration of the kit.

The Pipesmith CI report page in the light theme. The header reads 8 stages, 17 tools, 7 findings and gate passed. A totals table counts the findings per tool by level, 2 warnings and 5 notes in all. The tests table shows 148 tests, 0 failed, 2 skipped and 91.4 percent line coverage against a minimum of 80 percent. The Pipesmith CI report page in the dark theme. The header reads 8 stages, 17 tools, 7 findings and gate passed. A totals table counts the findings per tool by level, 2 warnings and 5 notes in all. The tests table shows 148 tests, 0 failed, 2 skipped and 91.4 percent line coverage against a minimum of 80 percent.
Passed Run Report Sample data A demo run that passes the gate: 148 tests without a failure, 91.4 percent line coverage against a minimum of 80, and only warnings and notes. Open in full sizeOpen in full size
The Pipesmith CI report page in the light theme. The header reads 8 stages, 17 tools, 26 findings and gate failed, with the reason "findings at or above error: 15 error". A totals table counts the findings per tool by level, 15 errors, 6 warnings and 5 notes in all. The failed tests and the low coverage count as errors of the test tool. The tests table shows 148 tests with 3 failed and 72.4 percent line coverage against a minimum of 80 percent. The Pipesmith CI report page in the dark theme. The header reads 8 stages, 17 tools, 26 findings and gate failed, with the reason "findings at or above error: 15 error". A totals table counts the findings per tool by level, 15 errors, 6 warnings and 5 notes in all. The failed tests and the low coverage count as errors of the test tool. The tests table shows 148 tests with 3 failed and 72.4 percent line coverage against a minimum of 80 percent.
Failed Run Report Sample data A demo run that fails the gate on 3 failed tests, 72.4 percent line coverage against a minimum of 80, and scanner errors such as a committed private key. Open in full sizeOpen in full size
Architecture of Pipesmith CI. A consumer workflow calls 8 stage workflows of the kit at one commit. Every stage job builds the kit tools in the Go image, plans the stage from the profile and the project file, runs the planned scanners as image steps pinned by digest, and writes one digest. lint runs lint, actionlint, hadolint. test runs test. sast runs semgrep, bandit, zizmor, gosec. deps runs osv-scanner, cargo-deny, govulncheck. secrets runs gitleaks. container runs trivy-config, kics, image, trivy-image. sbom runs syft. release runs syft, image, cosign. The report job merges the digests, applies the gate and writes findings.json, report.sarif, report.html and summary.md. Light theme. Architecture of Pipesmith CI. A consumer workflow calls 8 stage workflows of the kit at one commit. Every stage job builds the kit tools in the Go image, plans the stage from the profile and the project file, runs the planned scanners as image steps pinned by digest, and writes one digest. lint runs lint, actionlint, hadolint. test runs test. sast runs semgrep, bandit, zizmor, gosec. deps runs osv-scanner, cargo-deny, govulncheck. secrets runs gitleaks. container runs trivy-config, kics, image, trivy-image. sbom runs syft. release runs syft, image, cosign. The report job merges the digests, applies the gate and writes findings.json, report.sarif, report.html and summary.md. Dark theme.
Architecture A project workflow calls the stage workflows of the kit at one commit; each stage job writes one digest, and the report job merges them and applies the gate. Open in full sizeOpen in full size

Status

Version 0.1.0 of Pipesmith Registry can be downloaded below, and its source is public on GitHub. The table says what exists today and what comes next.

ProductTodayNext
Pipesmith Registry Reads existing file stores: Maven, npm, Docker pull and raw files, with sign in, an administration interface and a REST API. Deploy and proxy repositories.
Pipesmith CI A kit with scanners, a language model runner and an agent runner. The proof on a demo project, then a first release.
Pipesmith Suite Planned. Deciding which containers it starts.

Download

Pipesmith Registry 0.1.0 for macOS on Apple silicon, released on 12 November 2026.

Download for macOS on Apple silicon

Version
0.1.0
Released
File
pipesmith-registry-darwin-arm64
Size
13.3 MB
SHA-256
d014cb5b2de761c81e1af4501494eff0a0022a6610df8b6e369757a545a2eabe

Check the file after the download: shasum -a 256 pipesmith-registry-darwin-arm64 prints the SHA-256 above. The release is not signed. The checksum only shows that the download is complete.

The release page has the binaries for linux-amd64, linux-arm64 and darwin-arm64 and the file SHA256SUMS. The source is on GitHub, under the Apache License 2.0, and its README says how to start the server.