Which modules carry a component, and what that forces rebuilt

Goal: a Common Vulnerabilities and Exposures (CVE) record names a component and a version. List every easyconfig and installed module in one toolchain generation that carries it, then feed the recipes that contain it into the rebuild closure.

Run it

The recorded slice in this checkout is enough to see the counts. The files are copies of easybuild-easyconfigs develop 981d2123dddccca9ce0b15f9eb2643e872332f5e, the pin in scripts/fetch-upstream-trees.sh, and the upstream LICENSE is in that directory.

eb-stack component-reach \
  --component curl \
  --version '>=8,<9' \
  --generation 2026.1 \
  --easyconfigs tests/component_reach_recorded \
  --out-dir /tmp/component-reach

The command prints:

component=curl version=>=8,<9 generation=2026.1 reach=network-facing carriers=2 changed=1 must-rebuild=1 review=0 no-rebuild=1 out=/tmp/component-reach

cURL 8.17.0 is the module. git 2.52.0 depends on that cURL and is the no-rebuild row. The same command against the pinned easyconfigs tree and a deployed easystack uses scripts/fetch-upstream-trees.sh. Pass one of --component, --purl, or --cve.

scripts/fetch-upstream-trees.sh
set -a
source "${EB_UPSTREAM_CACHE:-$HOME/.cache/eb-stack/upstream}/env.sh"
set +a
eb-stack component-reach \
  --component curl \
  --version '>=8,<9' \
  --generation 2026.1 \
  --easyconfigs "$EB_EASYCONFIGS" \
  --easystack "$EB_EESSI_SOFTWARE_LAYER/easystacks/software.eessi.io/2026.06/eessi-2026.06-eb-5.4.0-2026.1.yml" \
  --out-dir /tmp/component-reach-full

The command prints:

component=curl version=>=8,<9 generation=2026.1 reach=network-facing carriers=23 changed=2 must-rebuild=1 review=133 no-rebuild=20 out=/tmp/component-reach-full

The changed files are cURL-8.17.0-GCCcore-15.2.0.eb and cargo-c-0.10.23-GCCcore-15.2.0.eb. The must-rebuild row is cURL/8.17.0-GCCcore-15.2.0, reason patched easyconfig. The summary’s reach= is the class of the component name: cross-user, network-facing, local-only, not-reachable, or unclassified when the built-in names do not include it. component-reach reads no site file. cross-user and network-facing justify a backport. cURL is network-facing.

--easystack and --installed narrow the walk to a deployed prefix. --filter-deps drops dependency tuples before the closure walk. When that flag is omitted and EASYBUILD_FILTER_DEPS is set, the command reads the variable. The recorded command above passes neither, so every easyconfig in the generation is the stack.

--component is the name. Matching ignores ASCII letter case, so curl matches cURL and jupyterlab matches JupyterLab. The match is a whole token, so jupyterlab does not match jupyterlab-server and curl does not match libcurl.

--version is an exact version, \* for any version, or a requirement such as >=8,<9. It is required with --component. With --purl it replaces the version in the URL. --cve does not take --version: the versions come from Open Source Vulnerabilities (OSV).

--purl is a package URL, for example pkg:cargo/rustls-webpki@0.102.8 or pkg:pypi/urllib3@2.5.0. The type selects which carriers count. generic and github match the easyconfig name: the module, a dependency, a builddependency, a component, a source, or a patch. pypi, cargo, npm, golang, and cran match an extension or a bundled component of that language. cargo also matches a crate, and pypi also matches a wheel. Any other type is rejected: the command exits 2 and the error says that purl type has no carrier model. pkg:cargo/curl and pkg:npm/curl do not match the cURL easyconfig. --component curl still matches that recipe by name. A version in the URL is the requirement unless --version is also passed.

--cve is a CVE id or another OSV id. The record is fetched from https://api.osv.dev/v1/vulns/<id>. A CVE record often has only a git range and no package. Advisory aliases (GHSA-, RUSTSEC-, PYSEC-, GO-) are followed, up to eight. Named tags such as libXpm-3.5.17 become exact versions. Git tags such as XORG-6_8_0 do not. Each affected package is searched on its own, and a version matches when any of that package’s requirements match or when it is one of the exact versions. A GIT range is mapped onto release versions from the affected entry’s versions list when that list is present, and otherwise from tags in the upstream repository (git ls-remote --tags and git merge-base --is-ancestor on a blobless fetch, cached, and skipped when the lookup cannot reach the network). A range that still does not parse is listed under Unresolved ranges in the markdown. It is not discarded. When every range on a package was unparsed, that package counts as review and its carrier list stays empty. The three output files are then one document with kind set to cve, and results contains one reach document per package. The summary line includes the closure counts changed, must-rebuild, review, and no-rebuild.

--generation is the toolchain generation, for example 2026.1 or 2025a. A recipe is in that generation when its toolchain version is that string, or when its toolchain is a member of the known foss hierarchy for that generation. GCCcore-15.2.0 and GCC-15.2.0 belong to 2026.1. GCCcore-14.2.0 belongs to 2025a, GCCcore-14.3.0 to 2025b, and GCCcore-13.3.0 to 2024a. A system toolchain does not. A module built with another generation is not a row.

--easystack-url repeats. The URL must be https://. The body is an easystack, read the same way as --easystack. Local files and URLs are one stack.

What carries it

  • the easyconfig’s own module name and version;

  • a dependencies or builddependencies tuple;

  • a bundle components entry;

  • a Python, R, or Perl extension in exts_list;

  • a Cargo crate, from a crates tuple or from a filename such as libz-sys-1.1.29.tar.gz, including a vendored +name-version fragment such as 0.4.89+curl-8.20.0. A Cargo recipe also matches a crate that appears only as a checksum key, such as rustls-webpki-0.102.8.tar.gz. The recipe’s own tarball is not that crate;

  • a Python wheel: a .whl filename in sources or checksums, an exts_list entry whose source is a wheel (pastel), or a top-level source_tmpl that names a wheel (cleo). The role is wheel;

  • a vendored or bundled filename in sources or patches whose name contains the component and a version;

  • a line in --compat-layer, name version or name==version, # comments skipped.

A dependency or a builddependency lists the recipe as a carrier and does not add it to the patched set. The component’s own module is the root, and those recipes are its closure. A module, bundle component, extension, crate, source, or patch means the recipe contains the bytes, and that filename is a patched root.

The compat layer is not an easyconfig. Pass it with --compat-layer. A hit is a row with an empty easyconfig and a note that it has no rebuild edge.

--filter-deps drops dependency tuples before the closure walk, the same way as rebuild-set, and does not strip exts_list. When the flag is omitted and EASYBUILD_FILTER_DEPS is set, the command reads it.

The closure

With no --easystack, every easyconfig in the generation is the stack. With no --installed, every module in the generation is treated as installed, so the reverse walk does not stop. Pass both when the question is a mounted prefix: then only those modules are visited.

The closure is the rebuild set of the containing recipes, inside the generation. Classes are the same as rebuild-set: must-rebuild, review, and no-rebuild. This command does not read a prefix or scan static symbols.

Dependencies resolve over every recipe in the trees, so a recipe on gfbf-2026.1 or gompi-2026.1 reaches the GCCcore-15.2.0 cURL through the SYSTEM definition of its toolchain. A dependency that no recipe resolves is listed in closure_unresolved in the JSON and TOML files, as the module and the requirement, and the closure has no edge for it. Without --filter-deps, a stack that takes zlib or binutils from its compatibility layer lists them for every recipe that names them.

Read the three files

out/component-reach.md is the carrier table and the closure table. out/component-reach.json is the same document. out/component-reach.toml starts with # Generated by `eb-stack component-reach`. Schema version 1. See output formats.