Skip to content

fix(scan): render readable report text - #1605

Open
John-David Dalton (jdalton) wants to merge 1 commit into
v1.xfrom
fix/scan-report-text-v1x
Open

John-David Dalton (jdalton) wants to merge 1 commit into
v1.xfrom
fix/scan-report-text-v1x

Conversation

@jdalton

@jdalton John-David Dalton (jdalton) commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Make socket scan report readable in terminals and CI logs with a plain-text health summary and alert table.

Tests cover formatting and a 200,000-alert report. Continues #1601.

Automated review notes

[!NOTE]
Low Risk
CLI report presentation only; JSON, Markdown, short output, and exit-code behavior are unchanged.

Overview
Default socket scan report text output no longer dumps the raw report object via logger.dir; it now renders a structured plain-text report with health status, aligned settings labels, and an alert table (URLs on separate lines).

Alert flattening is extracted into flattenReportAlerts and reused by both the new toPlainTextReport path and toMarkdownReport, so Markdown and text stay consistent. A new Vitest suite covers formatting (no ANSI/Map dumps, Unicode, column alignment, empty alerts, license/fold settings) and a 200k-alert regression to avoid argument-count failures when building large reports.

Reviewed by Cursor Bugbot for commit bf05dae. Configure here.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant