Find the insights and best practices about our product.
2026.4.1 Release Notes

Release #: 2026.4.1

Release Date: April 8, 2026

What's New

This release introduces cross-BOM package search for rapid vulnerability response, expands language coverage in CodeSensor and Detect AI, and adds filtering to vulnerability exports.

Technology Package Search

A new Technology Search tab on the Bill of Materials page lets you search for any package by name across all BOMs in your tenant in a single query. Results include the package name, version, BOM name repository URL, last scanned date, and file path. A CSV export is available directly from the results table.

Search is case-insensitive and matches partial strings, so entering a package name fragment returns all BOMs containing packages that match. Results are scoped to your tenant and reflect the most recent scan data for each repository.

Java Support in CodeSensor

CodeSensor now detects Java technologies, AI models, and datasets within repositories, closing a coverage gap for AI systems that include Java components. No configuration changes are required. Trigger a new scan on any repository to pick up Java components, with results visible in the BOM detail view.

Expanded Language Support in Detect AI

Detect AI now supports JavaScript, TypeScript, and Java to broaden the range of codebases it can analyze. Detection is automatic and applies on the next scan with no configuration required.

Filtered Vulnerability Exports

The Vulnerabilities page now includes two new options to filter by AI System and Bill of Materials. These let you narrow the vulnerability list to a specific scope before running an export. When you're ready to export, the export modal gives the option to apply your current filters to the download or to export all data. Targeted exports make it easier to share relevant findings with the right teams.

Bug Fixes

  • AI Card publishing: When sending an AI Card to a tenant that already existed as a recipient, the card failed to appear for the recipient. This has been resolved.
  • BOM filters: The "Unscanned" status filter on the BOM list page was returning incorrect results. Filtering now works as expected.
  • Duplicate AI Card notifications: Publishing an AI Card was triggering multiple duplicate email notifications to vendors. Notifications are now sent once per publications.
  • BOM detail search input: The search field on the BOM detail page lost focus after the first keystroke, requiring users to re-click the field before continuing to type. Focus is now maintained correctly.
Did this answer your question?