feat(runtime): align runtime scans table with Sysdig Secure - #75
Merged
Merged
Conversation
Fixes GHSA-rfgv-xxqx-mfg5 and GHSA-w293-vg96-wgc3 pulled in transitively via @module-federation/dts-plugin, which fail the high-severity audit gate.
The same image running in several clusters showed up as seemingly duplicated rows with different in-use counts, the columns weren't self-explanatory, and severity chips were unreadable in dark mode. Mirror the Secure runtime view so users can map what they see in Backstage to Secure: cluster/namespace per row, In Use / Vulnerabilities / Policy Evaluation / Component Lifecycle / Exceptions columns with the same order, compact severity bars and header tooltips. Accepted (exception) results show as passed with an exception marker. Sorting on rendered columns never worked because cells were JSX and the column definitions were rebuilt every render; sort on raw values with a severity-aware comparator instead.
tembleking
enabled auto-merge (squash)
September 30, 2026 11:08
mateobur
approved these changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Users couldn't make sense of the runtime scans table: the same image running in several clusters looked like duplicated rows with different in-use counts, "failed" and Severity vs In Use weren't self-explanatory, yellow chips were unreadable in dark mode, and sorting by Severity/In Use didn't work.
Mirror the Sysdig Secure runtime view so what users see in Backstage maps 1:1 to Secure: cluster/namespace per row, the same columns and order (In Use, Vulnerabilities, Policy Evaluation, Component Lifecycle, Exceptions), compact severity bars and header tooltips. Results with an exception (
accepted) show as Passed with an exception marker. Registry and Pipeline tables get the same bars and order for consistency.Sorting never worked on those columns because cells were JSX and column definitions were rebuilt every render, which resets material-table's sort state. Columns are now static and sort on raw values with a severity-aware comparator.
Also pins
undicito^7.29.1(transitive via@module-federation/dts-plugin) to clear two high advisories that fail the audit gate, and bumps to 1.6.0 to release.