Skip to content

fix(report): label package versions - #1613

Open
John-David Dalton (jdalton) wants to merge 2 commits into
fix/scan-report-large-outputfrom
jdalton/report-version-main
Open

John-David Dalton (jdalton) wants to merge 2 commits into
fix/scan-report-large-outputfrom
jdalton/report-version-main

Conversation

@jdalton

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

Copy link
Copy Markdown
Collaborator

Summary

  • Label the package version value as Version in text and Markdown scan reports.
  • Keep the existing unknown-value fallback and add renderer coverage for folded and multiple-version output.

Validation

  • Renderer unit tests, typecheck/build, scoped lint, and format checks passed.

Note

Low Risk
Presentation-only rename of report columns and row fields; behavior for version values and unknown fallbacks is unchanged aside from labeling.

Overview
Scan policy reports (plain text and Markdown) now label the third alert column Version instead of Introduced by, and the shared ReportAlertRow field is renamed from introducedBy to packageVersion (still sourced from the same nested-map key, with <unknown> when folding hides it).

isFullScanReport is exported later in the module; formatAlertTable’s column-width loop is refactored without changing layout. Unit tests and snapshots are updated, including coverage for version/file/package fold modes and multiple package versions.

Reviewed by Cursor Bugbot for commit de6b3af. 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