review-type-safety

To audit TypeScript code for type safety, run a targeted review on specified file paths or branch diffs to surface unsafe any/unknown usage, missing type guards, and unchecked discriminated unions. This generates structured findings with severity levels and concrete improvement suggestions.

Common type safety issues in TypeScript include the use of unsafe any or unknown types, missing type guards for runtime validation, and unchecked discriminated unions. Identifying these holes during static analysis strengthens compile-time guarantees and prevents runtime crashes.

Yes, you can run a type safety review on a specific git diff. The analysis is scope-aware, allowing you to focus on explicitly provided file paths or changes against a base branch, which reduces noise in large repositories by only reporting relevant type holes.

Type guards and discriminated unions improve TypeScript static analysis by enabling the compiler to narrow types safely at runtime. Auditing code for missing type guards and unchecked discriminated unions ensures type safety holes are caught early, providing stronger compile-time guarantees.

The type safety audit focuses on TypeScript projects with strictness considerations, flagging risky patterns like any or unknown usage. While no specific dependencies are required, enabling strict compiler options in your project enhances the effectiveness of the static analysis findings.

The best way to fix unsafe any and unknown types in TypeScript is to replace them with explicit, narrowed types using type guards or discriminated unions. The audit provides actionable reporting with rationale and concrete improvement suggestions to resolve these type holes.