kapsl Index
Docs Releases

flex

1 tool · 1 release line

Generate a fast lexical analyser in C or C++ from a rule file. 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 flex from flex@latest → 2.6.4 stable

Findings

M1

identical on amd64, arm64 — one table describes both

CVE Sev CVSS Affects Description
CVE-2019-6293 ↗ M 5.5 flex An issue was discovered in the function mark_beginning_as_normal in nfa.c in flex 2.6.4. There is a stack exhaustion problem caused by the mark_beginning_as_normal function making recursive calls to itself in certain scenarios involving…

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

Composition

default + m4
runtime none — self-contained
composes m4

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/flex:2.6.4
digest
platforms
size <1 MB unpacked · 1 layer
base scratch
signed cosign · verified
last scan

Sandbox boundary

flex

capabilities

rw

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

none

env passed through

none

none

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

env set by kapsl

1 set

M4

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.

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