Repository navigation
fix(security): keep the estimated severity inside the open leads column - #2465
Merged
Merged
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.
estimatedSeverityBadgerenders the estimate alone in the dashed outline badgefindingItemends withunverifiedChipfor unverified leads and its title column grows
What was checked
estimatedSeverityBadgeis only reached underisUnverified(view-overview.ts:509), sobucketOfalways yields a real severity label- Longest labels stay inside
w-16: badgetext-sm/text-xswith 3px padding is ~55px for "Critical" (badge.styles.ts:20) isUnverifiedand 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.
Loading