Skip to content

Dependency Security

Threadmill’s dependency-security job fails when it finds a known vulnerability in a pull request, a nightly scan of main, or a tagged release. Repository branch protection is configured separately and determines whether a failing pull-request check blocks a merge. The Gradle dependencySecurityScan task is the single entry point for the scan.

The task asks Git for every tracked *gradle.lockfile and *package-lock.json, then passes each file explicitly to OSV Scanner. A Git checkout is required: untracked local lockfiles are intentionally excluded, and exported source trees fail with an actionable error because they cannot prove which inputs are release evidence. Git-add any new lockfile so the local gate includes it; a release run additionally requires the clean, committed tree specified by the release checklist. Modifications to an already tracked lockfile are scanned from the working tree.

The input set includes buildSrc/gradle.lockfile, which carries the resolved build-classpath graph. It also includes settings-gradle.lockfile; that file currently contains only Gradle’s empty catalog marker, but keeping it in the enumeration prevents future settings dependencies from escaping the gate. The task deliberately excludes the version catalog and historical entries in Gradle checksum-verification metadata.

OSV Scanner fails the build on any advisory, regardless of severity. The same task runs npm audit --package-lock-only --audit-level=low, so every npm advisory at low or above also fails. CI and the tag-release workflow use Node 24.20.0/npm 11.19.0, install OSV Scanner 2.5.0 from its architecture-matched release binary, verify its SHA-256 checksum, and run the task with scanning required before testing or publishing.

There are no exceptions at present. If an advisory cannot immediately be removed, an exception may be added to osv-scanner.toml only after its exact version and reachable call paths have been reviewed. It must use one [[IgnoredVulns]] entry naming one advisory ID, a concrete reason, and a near-term ignoreUntil date. Package-wide overrides and permanent ignores are not allowed. The exception must be removed on expiry or as soon as a compatible fix exists, whichever comes first.

npm audit has no ignore mechanism in this repository. A vulnerable npm dependency must be upgraded, removed, or temporarily pinned to a patched compatible release through the overrides field in package.json. An override must name the affected package and patched version, explain its advisory in the pull request, and be removed when the direct dependency adopts the fix.

gradle/verification-metadata.xml is intentionally additive when dependencies change. Historical checksums authenticate previously resolved artifact bytes; they do not approve a version and are not vulnerability-scan inputs. The committed lockfiles define the current graph, and OSV Scanner evaluates that graph on every gated run. Regenerating verification metadata from scratch is a separate trust-policy change because it creates broad, unrelated checksum churn; do not mix it into a routine dependency upgrade.

The following assessment was refreshed on 2026-10-06. Re-run it whenever the dependency graph or the relevant code paths change.

Dependency surface Advisories assessed Reachability and decision
Vitest test tooling GHSA-82fw-gwwq-j7x9 Vitest and its mocker execute during UI development and testing, not in the packaged static dashboard. The audit resolved vulnerable 4.1.7 packages; Vitest is now pinned to the patched 4.1.11 release and the lockfile updates its matching packages. Test scope does not exempt the graph from either dependency gate.
Lettuce and Netty GHSA-5pvg-856g-cp85, GHSA-676x-f7gg-47vc, GHSA-xmv7-r254-6q78, GHSA-c653-97m9-rcg9, GHSA-cm33-6792-r9fm, GHSA-mfg7-5gfp-c4w3, GHSA-x4gw-5cx5-pgmh, GHSA-3qp7-7mw8-wx86, GHSA-558v-64gr-wgg4, GHSA-mj4r-2hfc-f8p6 Lettuce 6.8.2.RELEASE declares Netty 4.1.125.Final, where these ten advisories affect the resolved Redis graph. Hostname-based Redis connections may exercise netty-resolver-dns and netty-codec-dns: three advisories permit DNS cache poisoning, while two concern DNS validation or decoder resource handling. TLS connections may exercise the netty-handler hostname-verification defect. Five of the ten findings are in the two DNS artifacts newly added by Lettuce 6.8. Threadmill does not use the affected server-side SNI/subnet-filter or compression-decoder paths, but upgrades the complete Netty graph rather than suppressing them. The resolved security floor is Netty 4.1.137.Final; remove the explicit BOM only when Lettuce’s own transitive floor reaches that version.
Dashboard CSS toolchain GHSA-vfj7-8cjw-p6xm, GHSA-rj75-hqrm-r3gf, GHSA-68fv-2mgg-jv7q Tailwind 3.4 resolved braces through fast-glob, micromatch and chokidar. Every braces release is affected and none is patched, so neither an override nor an exception could clear it. Tailwind 3.4 also resolved postcss-selector-parser 6.x through postcss-nested. The dashboard build moved to Tailwind 4.3.3 through @tailwindcss/vite, whose Oxide scanner and Lightning CSS pipeline use none of these packages. The PostCSS config and Autoprefixer were removed. source-map-js, still reached through Vite’s PostCSS, Tailwind’s node helper and jsdom, is locked at the patched 1.2.2 within those dependents’ existing ranges, so no overrides entry is needed. These packages run only during dashboard builds and tests; the JAR ships compiled CSS.
Dashboard JavaScript toolchain GHSA-73wf-gq98-2v4g, GHSA-c83g-rgw3-j3cx, GHSA-w9m9-85wc-3x92 Vite 7.3.6, Babel 7.29.7, and esbuild 0.28.1 were already patched on main before this change. This change removes the remaining audit findings by moving Browserslist to 4.28.9 and PostCSS Selector Parser to 6.1.4. These packages run only during local or CI dashboard builds; the published JAR contains compiled static assets, not the toolchain. Build-time execution is still trusted code execution, so vulnerable transitives are upgraded rather than ignored.
Spring test stack GHSA-qv9r-c865-cp47, GHSA-9xv2-5v5q-p794, GHSA-gcx9-497g-6cp6, GHSA-h3x4-894j-xpx5, GHSA-5gvw-p9qm-jgwh Embedded Tomcat, Log4j, and Logback appear only in test compile/runtime lock entries and are not shipped in Threadmill artifacts. They still execute during CI integration tests. Spring Boot is upgraded to 4.0.8, its Spring Framework/Security pins are aligned, the catalog’s Logback pin now matches Boot’s resolved 1.5.38, and Tomcat is constrained to the patched 11.0.25 floor rather than treating test scope as an exception. Boot 4.0.8 now resolves Jackson 3.1.5 itself, so the earlier explicit Jackson constraint is removed.
Jackson 2 and Jackson 3 GHSA-7hhh-6rmp-j9qf, GHSA-p6pp-m3f8-5c89, GHSA-cxp5-3px4-pw24, GHSA-wv8q-qhhj-9h54, GHSA-gx83-3vf8-gh7j, GHSA-q4xh-88c3-wmh7, GHSA-wjgm-6hv5-3cvf Jackson 2 (com.fasterxml.jackson) 2.21.5 was resolved in every module and is a runtime dependency of threadmill-core: JsonJobSerializer parses every persisted job body and the dashboard deserializes operator-supplied job definitions, so the affected jackson-core / jackson-databind code is treated as reachable. The catalog moves Jackson 2 to 2.21.7, the earliest release fixing all seven advisories; Gradle’s Jackson BOM alignment carries jackson-datatype-jsr310 and the transitive jackson-dataformat-yaml to the same version. Jackson 3 (tools.jackson) 3.1.5 enters only threadmill-dashboard-spring’s test and browser-test classpaths through Spring Boot 4.0.8, which is not shipped in Threadmill artifacts but executes during CI. No Spring Boot 4.0.x patch release newer than 4.0.8 exists, so jackson-core and jackson-databind are constrained to 3.1.7 in test scope rather than taking a Boot minor upgrade. Remove that constraint when Boot’s BOM resolves Jackson 3 >= 3.1.7.

The standalone threadmill-metrics graph keeps Micrometer core, commons, and observation aligned at 1.15.12. The Spring modules resolve commons and observation together at Spring Boot’s 1.16.7 floor; those module build graphs are separate, and a downstream Spring application uses its Boot BOM to align Micrometer core as well. The mixed repository-wide minors therefore do not represent one mixed runtime classpath.

When evaluating a new report, confirm the resolved version in the committed lockfile, the affected module and configuration, whether application or build inputs can reach the vulnerable behavior, and the earliest compatible upstream fix. Lack of reachability may justify only a short-lived, advisory-specific exception; it does not justify a package-wide suppression.