null-as-error-cc

Detect silent error swallowing by scanning for catchAll and Effect.ignore patterns that return sentinel success values like null, false, or void. A ripgrep-driven Bun scanner locates these candidates and emits structured JSON hits for audit review.

A null-as-error pattern occurs when catchAll or Effect.ignore handlers collapse real failures into sentinel success values such as null, [], false, or void. This makes errors invisible to callers and severely hampers observability and debugging in Effect-based services.

Yes, you can run static analysis code audits on Bun TypeScript repositories. The scanner applies ripgrep to locate catchAll and Effect.ignore patterns, enriches hits with enclosing function names and export status, and spawns a read-only auditor to classify severity.

Yes, the scanner supports suppression marker detection to reduce false positives. Each identified hit is enriched with surrounding context, enclosing function name, export status, and suppression markers before the auditor classifies severity and recommends fixes.

You need bun, jq, and rg installed to scan for Effect.ignore patterns. The Bun runtime executes the scanner, ripgrep locates the static patterns, and jq processes the structured JSON output for the read-only auditor workflow.

Generate a classified audit report for pre-merge checks by running the scanner on the src directory. It synthesizes a final report listing error counts, severities, suppressed occurrences, and a decision-linked summary table with recommended fixes.