Repository navigation
fleetreach 1.5.0
Added
- Repo context and SSVC decisions (spec 08).
[[repo]]takesexposure,
mission_impact,safety_impact,ownerandtags, with[settings.context.defaults]
for the rest. Each vulnerable occurrence then gets a CISA SSVC deployer decision
(immediate,out-of-cycle,scheduled,defer) from KEV exploitation, the advisory's
CVSS vector (Automatable) and the repo's exposure and impact, through the published
ssvc:DT_DP:1.0.0table, tested row by row against CERT/CC's data.-f ssvclists the
decisions with their vector and reason;fix-firstandremediationsort by them; SARIF
results carry the outcome and take their level from it;-f ownerssplits the fix queue by
owner.--fail-on-ssvc <outcome>gates on them and, given alone, replaces the default
severity gate. Fail-closed throughout: without KEV data nothing is decided (and the gate
exits 2), missing context takes the most urgent values, and only a soundNotReachableor a
phantom dependency lowers a decision todefer.[settings.ssvc] poc_epssoptionally
counts a high EPSS as a public proof of concept. - Findings carry the advisory's
cvss_vector(additive JSON field). - SSVC, continued (spec 08). CISA Vulnrichment supplies CISA's own Exploitation and
Automatable per CVE where it has assessed one (fetched under--enrich, cached a day, or
read from a clone with--vulnrichment-dir); it only ever raises Exploitation.
[settings.ssvc] tableloads your own decision table in CERT/CC's CSV layout, validated to
cover all 72 combinations and recorded ascustom:<sha256>.impact,blastand
packages(andpackages-json) show the most urgent outcome and a reach weighted by it
([settings.ssvc] weights, default 8/4/2/0), and rank by it.[[source]]takes the same
context fields for every repo it discovers. - Upgrade risk from fleet evidence (spec 13, phase 1). Each remediation upgrade is rated
low(within the current major),medium(breaking, but at least 3 repos already run the
target or newer in its major) orhigh, with the reasons and the evidence (repos,
newest).-f remediationshows a Bump risk column,remediation-jsontherisk,
risk_reasonsandevidencefields, andfix planedits and pull request descriptions
carry the risk. The JSON report gainspackage_versions: the versions of each vulnerable
package that the fleet's lockfiles hold, and in which repos. bun.lockis read in full (bun 1.2+, lockfile versions 0 and 1): workspaces, nested
copies resolved the way Node loads them, dev scope and dependency paths. Checked against
osv-scanner on opencode, midday, elysia and bun's own lockfile: the same 4,829 registry
packages. The binarybun.lockbis still reported as partial coverage.- SPDX output and vulnerabilities in the SBOM (spec 05).
fleetreach sbom -f spdxwrites
SPDX 2.3 JSON (purls,DEPENDS_ONandDEV_DEPENDENCY_OFrelationships, coverage in
comments, a content-derived namespace).--report report.jsonembeds a saved scan's
findings: CycloneDXvulnerabilities[]with ratings,affects, KEV, EPSS and SSVC
properties and ananalysisthat isnot_affectedonly for a sound verdict (static
NotReachable:code_not_reachable; phantom:requires_dependency), or SPDXSECURITY
advisory references. Both formats pass their official schemas, and an SPDX document scans
back to the same findings. - Scan history, trends and SLAs (spec 09, phases 1 and 2).
scan --history-dir DIR
records each run as a gzipped snapshot plus an index of every finding's first and last
sighting and fix.fleetreach history trend|age|sla|mttrreads it: open findings per run
by severity, SSVC, ecosystem or owner; the oldest open findings; breaches of a
[settings.sla]policy keyed by SSVC outcome or severity (history slaexits 1 on a
breach, 2 without a policy); and time to fix. Fail-closed: a run that exited 2, an errored
repo or a partly-read source never marks a finding fixed, ignored findings are recorded as
ignored, and--history-dirrefuses the flags that drop findings.[settings.history] keepprunes old snapshots while the index keeps first-seen dates; a lost or stale index is
rebuilt from the snapshots. - Notifications (spec 09, phase 3).
fleetreach notify --history-dir DIRreports what
the newest run changed (new findings, fixed findings) and every breach of[settings.sla]
(with-c), grouped by owner. It prints, or POSTs to--webhook(HTTPS; network builds),
a stablefleetreach-notify/1JSON payload or, with-f slack, a Slack Block Kit message;
a webhook gets nothing when nothing changed unless--always.--github-issues(gh) or
--gitlab-issues(glab) with--repokeeps one issue per owner, found again by a hidden
marker, rewritten each run, closed when the owner has nothing open and reopened when a
finding comes back. A gap run never makes old findings look new. - Static HTML report (spec 09, phase 4).
fleetreach report html --history-dir DIR -o fleet-report.htmlwrites one self-contained page (no external resources) to host
anywhere: summary tiles, open findings per run by severity with gap runs marked, SLA
breaches, a queue per owner, fix campaigns from a savedfix status(--fix-status) and
time to fix by severity. Light and dark, usable at phone width, deterministic for a given
history. - GitLab merge requests for
fix apply --open-prandfix status, throughglab:
the open merge request from afleetreach/*branch is updated, otherwise one is created.
The forge is read from each repo'soriginhost, or set with--forge gitlab|github.
fix statusrows gain aforgefield and GitLab states are reported asOPEN,MERGED
andCLOSED, like GitHub's. - Fleet novelty signal (spec 10, phase 4). With
--signalsand--history-dir,
fleetreach:new-to-fleetflags packages whose name no earlier recorded run of the fleet
has read, the cheap early sign of a planted dependency (strongest next to a typosquat or a
recent release). Each history snapshot now records the package names it read, and the
index keeps them past retention. The first run that records names is the baseline and
flags nothing. - Maven mirrors from
settings.xml(spec 04).--maven-fetchfetches POMs through
the mirror of Maven Central that~/.m2/settings.xml(or--maven-settings FILE) names,
chosen with Maven'smirrorOfrules, with credentials from the matching<server>and
${env.NAME}expansion. A configured mirror that cannot be used (plain HTTP, encrypted
password, unset variable) stops the scan instead of falling back to Maven Central.
sbomandlicensestake--maven-fetchand--maven-settingstoo. - Fixes on an older line (spec 13). Remediation items list
alternatives: for repos
still on an older major (or0.xminor) than the target, the smallest version on their
own line that clears their advisories, with what it leaves open and the fleet evidence.
-f remediationshows them under the action (or 1.4.2 on 1.x (3 repos)), andfix plan
gives those repos a low-risk lock bump to it instead of a blocked breaking upgrade. Plan
edits are now marked breaking per repo: a repo on an older line crossing a major is
breaking even when the fleet's newest version is not. fix applyfor Go and uv (spec 07). Go modules are bumped withgo get <module>@v<to>, thengo list -deps -test ./...records the checksums the build needs
(both withGOTOOLCHAIN=localandGOWORK=off), anduv.lockwithuv lock --upgrade-package <pkg>==<to> --no-build, so neither runs package code; both are
verified by the re-scan like Cargo and npm. A raisedgodirective is named in the result,
the commit and the pull request, which now also say what the update ran.- Go from the osv.dev export (spec 01, phase 3). Without govulncheck, the module-level
Go scan readsGo/all.zipfrom--osv-diror the default cache like every other
toolchain-free ecosystem, sofleetreach db syncnow covers Go and no separate
vuln.go.dev mirror is needed.--go-vuln-db=file://still takes a mirror (or an unzipped
export). OnlyGO-records are used, so GHSA copies are not double-counted; an export
with noGO-record is an error, not a clean database. - A new website (spec 15): docs, guides, integrations, use cases, dated comparisons and
examples in one Astro Starlight site, replacing the mdBook docs. Every example is real
output from a frozen demo fleet (website/demo), regenerated bynpm run examplesand
checked in CI, as is the CLI reference generated from--help. Each page has a Markdown
copy, and the site publishesllms.txt,llms-full.txt, a sitemap and JSON-LD. Old
/docs/*.htmladdresses redirect. The README is shorter and points to the site.
Changed
- Faster on large lockfiles and large fleets, with byte-identical output (checked on a
10,471-repo fleet and 13 large open-source monorepos):- Dependency chains are built from one walk of each lockfile's graph instead of one walk per
package. npm, Hex and Julia asked for a chain for every package, so a big lockfile was
quadratic: the 13-monorepo scan went from 9.2s to 2.7s. sbombuilds each repo's inventory and BOM in parallel, and reads each crate's or NuGet
package's license once per run instead of once per repo: 37s to 4.3s on the 10k fleet.
With--fetch-licenses, deps.dev is asked once per package for the whole fleet, not once
per repo.licensesreads repos in parallel too.--signalsreads repos in parallel: 16s to 5.2s on the 10k fleet.- The OSV databases a fleet needs load at the same time instead of one after another.
- Dependency chains are built from one walk of each lockfile's graph instead of one walk per
Fixed
Found by checking each feature against real repos (gitea, caddy, hugo, spring-petclinic,
elysia, a FastAPI template, pydantic-ai) and independent tools: govulncheck, osv-scanner,
the osv.dev API, pyspdxtools, and CISA's and CERT/CC's own SSVC data.
- Go without govulncheck read only a module's first
affectedentry. 35 Go records list
a module once per release line (go-redis/v9 in GO-2025-3540), so a version only a later
entry covered was reported clean. Every entry now counts. An advisory naming several
modules (GO-2024-2606: pgx/v4 and pgproto3/v2) now reports each of them, not only the
first. - Safe versions stop where the bug comes back. The
patchedversions of a finding, in
every OSV ecosystem and Go, ended at the first fix, so a fix that a later release branch
re-breaks, or that only covers one of the record's release lines, counted as safe:fix planbumped grpc to 1.83.1, inside GO-2026-6443's re-introduced range, and could batch
js-yaml on 4.1.1, which GHSA-2883 still affects. Safe versions now account for every range
and everyaffectedentry for the package, and a batched bump moves up to the first
version safe for all its advisories (grpc 1.83.2, clearing six). - An advisory naming several packages (
@babel/helpersand@babel/runtime) gets a
remediation item for each; one of them used to disappear from the queue. - PyPI bounds with NVD-style suffixes (
2.6.0-NA,2.6.0-cu124) read as their release,
instead of leaving the range open (9 false positives on torch). - SBOM vulnerabilities on four-part versions (PyPI
1.2.0.0, NuGet1.2.3.4) now point
at their component. CycloneDX referenced a component that was not in the BOM, and SPDX
left the finding out. sbom,licensesand--signalsread apom.xmlthe wayscandoes, resolving
parents, BOMs and transitive dependencies, instead of only the declared dependencies:
spring-petclinic's SBOM listed 0 packages next to a scan that matched 171.- Workflows in a repo with packages were never scanned. GitHub Actions workflows were
read only when a repo had no package ecosystem, so a vulnerable action beside a lockfile
was missed: a false clean. They are now scanned in every repo that has
.github/workflows; without GitHub Actions advisory data, the repo gets a partial
coverage gap naming the workflows instead of an error. --whyonly searched Rust dependencies. It now finds a package in every ecosystem,
with its version, ecosystem, direct or transitive, and the chain that pulls it in.- Go findings made tables hundreds of columns wide. Affected function names are shown
without their package path, and the list is cut at 60 characters. - History runs were not reproducible under
SOURCE_DATE_EPOCH. The report's
generated_atused the clock, and a run's id hashes the report, so the same scan recorded
twice got different ids. It now followsSOURCE_DATE_EPOCHlike every other timestamp. history mttrshowed 0.0 days for a group with nothing fixed, which read as fixed at
once. The table shows-; JSON is unchanged.- SARIF results all pointed at
Cargo.lock, a file most non-Rust repos do not have, so
code scanning annotated nothing useful. Each result now names the file its package was read
from: the repo's lockfile in the order its reader tries them (bun.lock,uv.lock,
requirements.txtand so on), and for a GitHub Action the workflow that uses it. - The upgrade target could be a downgrade. The
→hint in tables, the SARIF message and
the VEX action took the first patched range, sosmallvec 1.6.0(patched in>= 0.6.14, < 1.0.0and>= 1.6.1) was told to move to 0.6.14. It is now the nearest fix above the
installed version. The fix queue already did this. - Hex: every package in a real
mix.lockwas direct. mix writes each dependency with an
options list,{:plug, "~> 1.14", [hex: :plug, ...]}, and the reader took the options list
for the dependency list, so it found none, and provenance chains were lost. Optional
dependencies also no longer make a package transitive: mix installs one only when something
requires it. - Advisory titles kept stray spaces from osv.dev (
cowlib cow_http_te module: ...),
which showed in tables. Whitespace in titles is now collapsed.