What's New

This release adds version history for Bills of Material, on-demand CloudSensor scans, and archived-repository exclusion in Detect AI, along with a new Public API endpoint to trigger CodeSensor scans. It also includes several reliability and security fixes.

Trigger CodeSensor Scans Through the Public API

A new Public API endpoint lets you trigger a CodeSensor scan for a specific Bill of Materials, so scanning can be wired directly into a CI/CD pipeline instead of waiting on the nightly schedule.

Triggering a scan returns a job id for reference; track progress from the existing Bill of Materials endpoint, which reflects the scan's status as it moves from queued to complete. A request for a BOM outside your tenant returns a 404.

Version History for Bills of Material

Bills of Material now keep a version history: every create or update captures a snapshot, giving you an auditable record of how a BOM has changed over time. A new Version History flyout on the BOM Details page lists each version's number, creation date, creator, and description. This release covers read-only history: restoring prior version or comparing two version side by side isn't available yet. Version capture is best-effort, so if it fails, the underlying BOM operation still succeeds and the failure is only logged.

On-Demand Discovery for a Single CloudSensor Connection

CloudSensor previously scanned every connection once a night. A new "Run scan now" action lets you refresh a single connection's inventory on demand, so you're not waiting on the clock or forcing a full rescan just to check one change.

Only one discovery job can run per tenant at a time, so starting a scan while another is already in progress, whether the nightly sweep or another connection's run, returns a conflict message rather than starting a second job. Scan-scheduling controls the platform didn't actually act on have also been removed from the connection manager.

Detect AI Excludes Archived Repositories

Detect AI now recognizes archived repositories and skips them in bulk scans and automatic Bill of Materials creation, since scanning code that can't change slows down scans of the repositories that do. Archived repositories still appear in your inventory, marked with an "Archived" badge, and the repository grid can be filtered to show active, archived, or all repositories.

Skipped archived repositories are marked with a visible, auditable reason in scan and auto-BOM job results. You can still manually create a BOM for an archived repository at any time, and existing BOMs for archived repositories are retained. This applies to GitHub, GitLab, Bitbucket Data Center, and Azure DevOps; Bitbucket Cloud does not report an archived status, so this doesn't apply there yet.

Bug Fixes

Fixed an issue where organization pickers used for AI Card recipients listed contacts of every type instead of filtering to the requested type.
Fixed an issue where an incremental code scan could return a stale Bill of Materials as though the scan had succeeded, when the comparison against the prior scan failed to resolve.

Did this answer your question?