Repo brief: railwayapp/nixpacks

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T18:14:36.858Z · commit 144b4f9ab1c3

Verdict

Healthy — Strong maintenance signals

• Last commit today
• 31+ active contributors
• Distributed ownership (top contributor 38% of recent commits)
• MIT licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Nixpacks generates OCI-compliant Docker images directly from application source code by combining Nix package management with Docker. It's a buildpack alternative that resolves system and language dependencies through the Nix ecosystem rather than buildpack detection, producing deployable images suitable for platforms like Railway. Core capability: source directory → pull Nix dependencies → emit ready-to-deploy container image. Monolithic Rust binary with modular provider architecture: src/providers/ contains language-specific detectors and build instructions (node.rs, go.rs, python implicit via detection), src/nixpacks/builder/docker/ handles Dockerfile generation and Docker image…

Start here

Read these in order:

• src/nixpacks/images.rs — Foundation: doesn't import anything internally and is imported by 2 other files. Read first to learn the vocabulary.
• src/nixpacks/plan/merge.rs — Foundation: imported by 2, no internal dependencies of its own.
• docs/components/SideNav.tsx — Built on the foundation; imported by 2 downstream files.
• docs/components/Hero.tsx — Built on the foundation; imported by 1 downstream file.
• examples/deno-fresh/fresh.gen.ts — Layer 2 — application-level code that wires the lower layers together.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/railwayapp/nixpacks.git
cd nixpacks
cargo build --release
./target/release/nixpacks --help

Requires Rust 1.60+ (per Cargo.toml), cargo toolchain, and likely Nix installation for full functionality (though not explicitly stated in manifest).

Daily commands:

# Verify Cargo.toml exists
cargo run -- build /path/to/app --output image:latest
# or debug:
cargo run -- plan /path/to/app

No explicit dev-server startup; this is a CLI tool. Tests run via cargo test (insta snapshots visible in dev-dependencies).

Key cautions & unknowns

• Scorecard: default branch unprotected (0/10)
• Nix availability required: Full functionality requires Nix toolchain installed (not just Rust); bare cargo build may succeed but runtime will fail on Nix invocations. Provider precedence matters:…
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.