code-critic

To find security vulnerabilities and performance issues during a code review, you can analyze code blocks to identify injections, unsafe inputs, and expensive algorithmic patterns. This process flags typing issues and security concerns across languages like JavaScript, Python, and Rust.

The best way to enforce strict typing in pull requests is through static code analysis that evaluates type correctness across languages. This analysis flags typing issues and type misuse directly within code blocks provided during the review process.

To triage code review findings into Critical, Warning, and Nitpick labels, analyze the code to categorize security vulnerabilities, performance concerns, and typing issues by severity. This labeling satisfies triage requirements for prioritizing module and library fixes.

Static code analysis works with Rust and TypeScript to identify Big-O performance concerns and inefficient loops. It evaluates code blocks fed into the prompt to flag expensive patterns and ensure type correctness across these languages.

You can get optional refactor suggestions for unsafe inputs and exposed secrets by analyzing your code blocks. The analysis identifies these security vulnerabilities and provides triage labeling to help you apply the suggested fixes.