Release Updates

Black Duck release updates

Every Black Duck release Merito has reviewed, newest first. Each update explains what changed, who it affects and what to plan before you upgrade.

Explore Black Duck licensing and services
Black Duck Detect 12.1.1: Updated inspection components for pipeline scans cover graphic
Black Duck

Black Duck Detect 12.1.1: Updated inspection components for pipeline scans

Black Duck Detect 12.1.1 updates Docker Inspector to version 12.0.2 and Project Inspector to version 2026.9.1. Teams running self-managed Detect should also account for the documented Java, download endpoint, Docker Inspector deprecation, and SCASS network requirements.

  • Black Duck
  • Detect
  • CI/CD
Black Duck Coverity 2026.9.0: Broader Sigma analysis for Kotlin, Groovy, and modern languages cover graphic
Black Duck

Black Duck Coverity 2026.9.0: Broader Sigma analysis for Kotlin, Groovy, and modern languages

Black Duck Coverity 2026.9.0 moves Kotlin analysis to Sigma autocapture, with existing Kotlin findings reopened as new issues and prior triage data lost. It also makes Groovy generally available, adds ECMAScript 2026 and TypeScript 7 support, expands compiler coverage, and includes cumulative Sigma checker content.

  • Black Duck
  • Coverity
  • AppSec
  • SAST
Black Duck Detect 12.0.0: Tighter Scan Scope and CRA Readiness cover graphic
Black Duck

Black Duck Detect 12.0.0: Tighter Scan Scope and CRA Readiness

Black Duck Detect 12.0.0 improves software composition analysis governance by adding controls for UV dependency groups, npm workspaces, Bazel dependencies, and empty scan results. Java 8 support is removed, Java versions below 17 are deprecated ahead of Detect 13.0.0, and Docker Inspector is scheduled for removal in 13.0.0. Enterprises should update CI runner standards, firewall allow lists, and scan policies before upgrading.

  • Black Duck
  • Detect
  • CI/CD
Black Duck Detect 11.5.1: Prevent missed Gradle dependencies in release BOMs cover graphic
Black Duck

Black Duck Detect 11.5.1: Prevent missed Gradle dependencies in release BOMs

Black Duck Detect 11.5.1 fixes a Gradle init-script regression in which phantom subprojects could receive an empty configuration set and report zero components. The release also resolves a component-location analysis exception triggered by spaces in version strings. For enterprises, the result is more dependable BOM evidence for release approvals, open-source risk decisions, and audit records.

  • Black Duck
  • Detect
  • CI/CD
Black Duck Detect 11.5.0: More Reliable SBOM Evidence Across Builds cover graphic
Black Duck

Black Duck Detect 11.5.0: More Reliable SBOM Evidence Across Builds

Black Duck Detect 11.5.0 strengthens software composition analysis evidence by correcting dependency parsing and build-tool edge cases that could produce incomplete or inaccurate BOMs. The release moves Quack Patch output into the Detect scan output directory, includes it in diagnostic archives, and adds operational guidance for renamed download domains, SCASS network access, CentOS deprecation, and the planned Java 8 support sunset. Enterprise teams should validate scan-success policies where empty BOMs are now an expected outcome for projects with no dependencies or no matching binaries.

  • Black Duck
  • Detect
  • CI/CD