Skip to content

fix(security): keep the estimated severity inside the open leads column - #2465

Merged
Makisuo merged 1 commit into
mainfrom
fix/security-open-leads-badge
Nov 10, 2026
Merged

Makisuo merged 1 commit into
mainfrom
fix/security-open-leads-badge

fix(security): keep the estimated severity inside the open leads column

869cc4f
Select commit
Loading
Failed to load commit list.
Maple Review Bot / Maple / review succeeded Nov 10, 2026 in 47s

Confidence 10/10 · No issues found

🟢 Confidence 10/10 · safe to merge. Pure markup change inside one row; the predicate guard and both call sites line up, and recent UI-only remaps of this file shipped without test edits.
no findings · tests not needed · risk low

The Open leads row now renders only the estimated severity in its fixed 64px column and moves the "Unverified" mark to a trailing chip, matching the findings list. Contained view change, safe to merge.

  • estimatedSeverityBadge renders the estimate alone in the dashed outline badge
  • findingItem ends with unverifiedChip for unverified leads and its title column grows
What was checked
  • estimatedSeverityBadge is only reached under isUnverified (view-overview.ts:509), so bucketOf always yields a real severity label
  • Longest labels stay inside w-16: badge text-sm/text-xs with 3px padding is ~55px for "Critical" (badge.styles.ts:20)
  • isUnverified and the chip use one predicate, so no row gets a severity without its chip

869cc4f · Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.