kapsl Index
Docs Releases

ripgrep

1 tool · 1 release line

Recursively search directories for a regex pattern, respecting gitignore. Every tool here carries the same sandbox boundary.

Release lines we maintain · the project decides these

findings shown are the whole project at that line

Tag Resolves to Lifecycle Updated Findings What the tag promises
  • stable — floats, carries security updates
  • unstable — tracks pre-releases, may break
  • eol — frozen, upstream is done

Tools in this project · pick one to inspect

all share one boundary

Tool Capabilities Seccomp Findings Image Description
showing rg from ripgrep@latest → 15.2.0 stable

Findings

clean

identical on amd64, arm64 — one table describes both

No known findings in this image at the last scan.

These are the findings of ripgrep, which ships every tool in this project. kapsl reports and gates; it never edits an image to clear a finding.

Composition

default + bzip2, gzip, xz-utils
runtime none — self-contained
composes bzip2, gzip, xz-utils

Some tools are only useful composed: a pip-installed CLI needs python as its runtime, bash pulls in coreutils. kapsl resolves that for you — -e git,python:flake8 composes explicitly.

Image

image ghcr.io/kapsl-sh/ripgrep:15.2.0
digest
platforms
size 5 MB unpacked · 1 layer
base scratch
signed cosign · verified
last scan

Sandbox boundary

rg

capabilities

ro

Filled is granted to every invocation; the rest need --cap at the point of use.

seccomp tier

per tool

default

The syscall filter applied to this tool's entry point. Tools sharing an image do not share a tier.

dotfiles mapped in

read-only unless noted

  • ~/.gitconfig
  • ~/.config/git/config
  • ~/.config/git/ignore

env passed through

1 forwarded

RIPGREP_CONFIG_PATH

Nothing else crosses in. No AWS_*, no SSH_AUTH_SOCK unless you ask.

env set by kapsl

none

none

per-subcommand

no overrides

Every invocation gets the same boundary. Where a tool needs more for one subcommand only, kapsl scopes it there rather than granting it everywhere.

Provenance

Every image ships a full SBOM and a signed build attestation. Nothing here is a claim you have to take on trust.

0 findings across this project at latest. Counted once per advisory across every image the project builds.