Skip to content

fix: retain runtime coverage for Semgrep TypeScript parse failures - #9

Merged
leemour merged 1 commit into
mainfrom
fix/security-scanner-coverage
Oct 10, 2026
Merged

leemour merged 1 commit into
mainfrom
fix/security-scanner-coverage

Conversation

@leemour

@leemour leemour commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

Pinned Semgrep can fail to parse entire modern TypeScript files. Preserve the original report, compile only those failed files with pinned esbuild, and scan their runtime JavaScript with source maps back to the original source. Compilation, parser errors or missing runtime coverage still fail the run; type-only syntax remains an explicit limitation.

Run scanners independently and keep Stop hooks disabled during continuation work. Validation: full lint, typecheck, coverage (100% lines), docs and Bun smoke passed; regression cases cover finding mapping, compiler/parser failures, missing coverage and outside-root paths. An archived public messaging snapshot recovered four full-file parser failures while retaining partial-parser warnings.

@leemour
leemour merged commit 1efa4d4 into main Oct 10, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant