kapsl Index
Docs Releases

libtool

1 tool · 1 release line

Install the libtool macros and ltmain.sh into a source tree. Every tool here carries the same sandbox boundary.

kapsl libtoolize
Source ↗ Registry ↗

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 libtoolize from libtool@latest → 2.5.4 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 libtool, which ships every tool in this project. kapsl reports and gates; it never edits an image to clear a finding.

Composition

default + m4, sed, grep
runtime bash, posix-essential
composes bash, posix-essential, m4, sed, grep

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

name libtool
platforms
size 2 MB unpacked · 1 layer
base scratch
signed cosign · · public key
findings last changed

Sandbox boundary

libtoolize

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.

host paths mounted in

read-only unless noted

none

env passed through

1 forwarded

LIBTOOLIZE_OPTIONS

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

env set by kapsl

5 set

ACLOCAL_PATHGREPM4SED_lt_pkgdatadir

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

sbom amd64 ↗ arm64 ↗
attestation amd64 ↗ arm64 ↗
scan report amd64 ↗ arm64 ↗
vex amd64 ↗ arm64 ↗

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.