The Hook
When a project transitions its Dependency Scanning pipeline to continuous SBOM-based ingestion (SBOM_INGESTED), a frontend state machine that fails to map inventory run-mode labels accurately will misreport automated remediation readiness across an entire organization's security inventory.
The Deep Dive
Modern DevSecOps pipelines are shifting from monolithic container-per-job scanners to CycloneDX Software Bill of Materials (SBOM_INGESTED) ingestion, where dependency graphs are parsed once and continuously evaluated against advisory databases. In GitLab's Security Inventory and Vulnerability Management architecture, platform engineers need immediate clarity on whether a project's dependency scanning coverage operates in automated (AUTO) or manual (MANUAL) triage capability mode.
While authoring MR !271086 (fix(security): use inventory run mode status labels), I traced how the security inventory's triageCapabilityStatus computed status labels when a project's coverage state reported SBOM_INGESTED. Previously, the status resolver did not consistently apply the inventory run-mode label mapping (coverage.runMode ?? 'AUTO') for SBOM_INGESTED states, creating a mismatch between what the backend coverage pipeline reported and how the Security Inventory UI rendered auto-triage readiness. By resolving coverage.runMode ?? 'AUTO' against the canonical inventory run-mode status dictionary in MR !271086, the inventory now accurately reflects both explicit MANUAL/AUTO configurations and default AUTO fallbacks.
This frontend state alignment pairs directly with backend read-model accuracy in vulnerability_reads. As I implemented in MR !269474 (fix(vulnerabilities): derive read link flags), once automated or manual triage links a vulnerability to an internal issue, external tracker (external_issue_links), or remediation Merge Request (merge_request_links), Vulnerabilities::Reads::UpsertService derives has_issues and has_merge_request with preloaded associations so the Security Dashboard reflects remediation progress in constant database query time.
The GitLab Hero Angle
From continuous CycloneDX SBOM_INGESTED coverage tracking (MR !271086) to N+1-free vulnerability_reads link derivation (MR !269474), GitLab unifies Software Bill of Materials ingestion, automated triage capability reporting, and remediation tracking in one cohesive DevSecOps control plane.
The Takeaway
Keep your security inventory UI state machines and backend read-model upserts tightly coupled to explicit enum fallbacks (coverage.runMode ?? 'AUTO') so transitions to SBOM-driven scanning never break triage observability.
