TypeScript strict mode enabled
Why it matters
Without TypeScript strict mode, the compiler silently allows implicit any types, skips null-safety checks, and misses a family of type errors that only surface at runtime. ISO 25010:2011 §6.5.4 classifies these as reliability defects. A single null dereference in an authentication path or payment flow can take down production. Strict mode is the umbrella flag — disabling it means noImplicitAny, strictNullChecks, and strictFunctionTypes are all off simultaneously.
Severity rationale
Critical because disabling strict mode silently opts out of the compiler's entire null-safety and implicit-any detection family, letting whole classes of runtime crashes ship undetected.
Remediation
Enable strict mode in tsconfig.json. Do not compensate by disabling individual sub-flags — that defeats the flag's purpose. To migrate an existing codebase without a full-stop build failure, temporarily set "noEmitOnError": false while you work through the errors one file at a time.
{
"compilerOptions": {
"strict": true,
"noUncheckedIndexedAccess": true
}
}
Use // @ts-expect-error (with a comment) to suppress individual stubborn errors during migration — never // @ts-ignore without context.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Code Quality Essentials Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- iso-25010:2011 · maintainability.modifiability — Maintainability — Modifiability
Taxons
History
- 2026-04-18·v1.0.0·Initial import from code-quality-essentials·automated
- 2026-04-20·v1.1.0·Add Phase 6.0 detect-jq snippet for deterministic tsconfig.strict parse·by cakleinman