vertti/preflight

vertti/preflight has 57 GitHub stars and 2 forks. Star changes are not measured yet. Last checked 2026-11-09 09:17 UTC. Last push 2026-11-04.

이 수치를 측정하는 방법

Validation toolkit for containers and CI. Single binary, zero dependencies.

57 스타 2 forks

측정된 스타 증가

in 24h: 업데이트 지연
in 7 days: 업데이트 지연
in 15 days: 업데이트 지연
in 1 month: 업데이트 지연

서로 겹치는 기간의 순증가량이며 일별 합계가 아닙니다. 측정값이 없으면 비워 둡니다. 스타는 관심도를 나타내며 품질을 보장하지 않습니다.

README.md

Original

Preflight

Validation toolkit for containers and CI. Single binary, zero dependencies.

demo

Quick Start

COPY --from=ghcr.io/vertti/preflight:latest /preflight /usr/local/bin/preflight

RUN preflight cmd node --min 18.0        # verify binary + version
RUN preflight env DATABASE_URL --hide-value  # env var exists, value stays out of the build log
RUN preflight file /app/config.yaml      # file exists
RUN preflight tcp postgres:5432 --timeout 5s  # reachable?

HEALTHCHECK CMD ["/preflight", "http", "http://localhost:8080/health"]

What It Does

Pre-flight checks for containers: verify services, environment, dependencies. Each check does multiple things and tells you exactly what failed.

One command, multiple checks — preflight cmd node --min 18.0 verifies: on PATH, actually runs, returns version, meets constraint
Works without a shell — Runs in distroless/scratch, no shell required
Container-aware — Reads cgroup memory limits and CPU quotas, not just host /proc/meminfo and core count
Version constraints — --min 1.0 and --range '^1.0' use semver, not string comparison

[OK] cmd: node
     path: /usr/local/bin/node
     version: 20.10.0

[FAIL] cmd: python
       version 3.9.0 < minimum 3.11

Exit code 0 on success, 1 on failure. Works with set -e, Docker RUN, and CI pipelines.

Use Cases

Docker builds — verify binaries, configs during image build
Startup — wait for databases before your app starts
CI — validate environment, connectivity, checksums
Health checks — HTTP/TCP without curl or netcat

FAQ

Why not just shell scripts?

Shell works for simple checks. But this:

# Check node exists, runs, and version >= 18
command -v node >/dev/null 2>&1 && \
  node --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+' | \
  awk -F. '{if ($1 >= 18) exit 0; else exit 1}' || \
  (echo "node missing or wrong version"; exit 1)

Becomes:

preflight cmd node --min 18.0

Preflight also helps when you need:

Checks in minimal images (no shell available)
Container-aware resource limits (cgroup detection)
Semantic version constraints (^1.0, >=2.0, <3.0)
Consistent output format across all checks

Does this add bloat/attack surface?

2.5MB binary (Linux, UPX-compressed), no C dependencies
5 runtime dependencies (cobra, pflag, semver, x/sys, x/term)
Security scans on every commit (govulncheck, gosec)
Auto-updated via Renovate

To exclude from final image: multi-stage builds

Why not curl for health checks?

Curl works. Preflight is useful when curl isn't in your image, or you need JSON path assertions, built-in retry, or you're already using it for other checks.

Install

In containers:

COPY --from=ghcr.io/vertti/preflight:latest /preflight /usr/local/bin/preflight

Want to keep your final image lean? See Keeping Containers Clean for multi-stage builds and external validation.

On your machine / CI:

curl -fsSL https://raw.githubusercontent.com/vertti/preflight/main/install.sh | sh

Other install methods

Usage

See the full usage guide for all commands and options.

Check commands

preflight cmd node                            # exists and runs
preflight cmd node --min 18.0                 # version constraint
preflight cmd ffmpeg --version-cmd -version   # custom version flag

All cmd options

Check environment variables

preflight env DATABASE_URL --hide-value          # exists and non-empty, value not printed
preflight env MODEL_PATH --match '^/models/'     # matches pattern
preflight env APP_ENV --one-of dev,staging,prod  # allowed values

All env options

Check files and directories

preflight file /models/bert.onnx --not-empty   # file exists and has content
preflight file /var/log/app --dir --writable   # directory is writable
preflight file /app/entrypoint.sh --executable # script is executable

All file options

Check HTTP endpoints

preflight http http://localhost:8080/health         # basic health check
preflight http https://api.example.com --status 204 # custom status code
preflight http http://localhost/ready --retry 3     # retry on failure

All http options

Verify file checksums

preflight hash --sha256 67574ee...2cf myfile.tar.gz  # verify SHA256
preflight hash --checksum-file SHASUMS256.txt app.tar.gz  # from checksum file

All hash options

Run checks from a file

Create a .preflight file in your project:

# .preflight
file /etc/localtime --not-empty
cmd myapp --min 2.0
cmd go
env HOME

Run all checks:

preflight run                             # finds .preflight automatically
preflight run --file /path/to/.preflight  # specify file explicitly

File format, discovery, and hashbang support

Security

Preflight is designed for security-sensitive environments like CI pipelines and container builds. We take code quality seriously:

gosec — Static analysis for security vulnerabilities
govulncheck — Dependency vulnerability scanning
20+ linters via golangci-lint including nil-safety and error handling checks

All security checks run in CI on every commit.

License

Apache 2.0