Skip to content

fleetreach 1.4.0

Choose a tag to compare

@github-actions github-actions released this 31 Oct 16:22
· 303 commits to main since this release

Added

  • SBOMs as a scan input. [[repo]] sbom = "build/bom.json" scans a CycloneDX (1.4 to
    1.6) or SPDX 2.3 JSON document instead of the repo's lockfiles, for builds fleetreach cannot
    read. Components are routed by purl to the ecosystem matchers (each feeder gained a public
    scan_installed), with direct dependencies and paths from the document's graph. Coverage is
    full only when CycloneDX asserts completeness; unscannable components are named. An SBOM
    from fleetreach sbom scans back to identical findings.

  • Fix pull requests. fix apply --push pushes each verified fleetreach/* branch, and
    --open-pr [--draft] opens a pull request for it with gh, or updates the open one on a
    re-run. The description lists the advisories, flags breaking jumps, states the
    verification and names the campaign's other repos. Unverified branches are never pushed.
    fix status lists the pull requests of every repo. Tested against a real private repo.

  • Typosquat signal. scan --signals also flags npm, PyPI and Cargo dependencies one edit
    from a popular package they are not, against bundled lists (17,338 npm, 15,000 PyPI and
    5,000 crate names, refreshed by scripts/update-popular.py). Registry-equivalent spellings,
    siblings in one npm scope and version-digit forks are not flagged. Measured at 1.6 flags per
    1,000 distinct names on real projects, all legitimate, so it stays opt-in.

  • Release-age signal (scan --release-age 72h). Warns on dependency versions published
    less than the given time ago, the question that matters during a worm outbreak. Publish
    times come from deps.dev (opt-in: it sends names and versions; cached), and a version
    deps.dev cannot date is listed separately, never treated as old. licenses --fetch and
    this signal share one deps.dev client and cache.

  • Maven transitive resolution. A pom.xml is resolved into the dependency tree Maven
    would build, in pure Rust and without running Maven: parent chains, properties,
    dependencyManagement and imported BOMs, default profiles, nearest-wins mediation with
    scope widening, exclusions, optional dependencies, version ranges and multi-module
    reactors. POMs come from ~/.m2/repository and a local cache; scan --maven-fetch also
    fetches missing ones from Maven Central (opt-in: it sends coordinates). Unresolvable items
    are named as partial coverage. Matched mvn dependency:list on test projects (25 of 25, and
    85 of 85 artifacts and versions for a Spring Boot project, with one scope label differing).

  • Supply-chain signals (scan --signals). Lockfile hygiene as warnings, read from files
    already parsed and with no network: install scripts (npm hasInstallScript), git, URL or
    path sources, registries outside the public ones or [settings.signals] registries
    (matched on the whole host, so lookalike hosts are caught), registry packages without a
    checksum, and third-party GitHub Actions pinned to a movable tag instead of a commit SHA.
    Opt-in, so existing reports and --fail-on-warnings gates do not change.

  • Known malware is first-class. OSV MAL- findings are always critical, are never
    hidden by --min-severity, and the remediation queue and fix plan say to remove the
    package and rotate credentials instead of suggesting a version.

  • License inventory and policy. fleetreach licenses gives every dependency's license
    (SPDX, with where it came from: composer.lock, package-lock.json, node_modules, the
    Cargo registry cache, virtualenv metadata, the NuGet cache) and a category (forbidden,
    restricted, reciprocal, notice, unencumbered). --fetch looks unknown ones up on deps.dev,
    opt-in because it sends package names, with a permanent local cache. A
    [settings.licenses] policy (allow/deny lists, per-category verdicts, unknown = "deny"
    by default, runtime scope, per-package exceptions with a reason) turns them into
    violations: exit 1 on a denied license. fleetreach sbom fills CycloneDX licenses from
    the same data. Cargo licenses agree with cargo-deny's on this repository.

  • fleetreach fix: verified fix branches. fix plan turns a saved report's
    remediation queue into per-repo edits (lock bumps, or blocked with the reason: no fix, a
    breaking jump without --allow-breaking, an unsupported ecosystem). fix apply performs
    each lock bump in a git worktree on a fleetreach/<campaign>/... branch with a lock-only
    command that runs no package code (cargo update --precise, npm update --package-lock-only --ignore-scripts, or a GitHub Actions tag rewrite), then re-scans:
    the commit is marked verified only when the targeted advisories are gone and nothing new
    appeared. Your work tree is never touched and nothing is pushed.

  • GitLab fleet sources. [[source]] kind = "gitlab" lists a GitLab group with all its
    subgroups (or a user namespace) on gitlab.com or a self-managed instance (api_url), with
    the same include/exclude globs, topics, archived and fork filters and sparse checkouts as
    GitHub. GITLAB_TOKEN (or token_env) authenticates private groups.

  • Stable SARIF fingerprints. Every result carries partialFingerprints keyed on the
    advisory, ecosystem, repo and package (not the version), so GitHub code scanning keeps one
    alert per finding with its history across scans and through bumps that do not fix it.
    Before, every result pointed at the same lockfile location, so code scanning could merge
    the same advisory across repos or packages into one alert.

Changed

  • Repo ids from fleet sources keep the full namespace path of nested URLs
    (group/sub/name, previously sub/name), so same-named projects in different subgroups
    no longer collide. A git source with a nested URL gets a new id, so a saved baseline
    or a [[repo]] override written against the old id needs updating.