Code Review
Typo’s built-in automated code reviews help you ship clean, secure, and high-quality code—faster. It scans your codebase and pull requests to identify potential issues, recommends improvements, and even auto-generates safe fixes before merging into the master branch.
With intelligent suggestions and hotspot detection, Typo ensures every merge is smoother and more reliable.
Read more about setting Code health here
AI-Based Code Review
Typo leverages Artificial Intelligence to provide automated code analysis directly within your development workflow. As soon as a Pull Request (PR) is created, our system automatically analyzes the code changes to identify potential issues, such as bugs, vulnerabilities, or deviations from best practices. The findings are then immediately posted as a clear and concise comment on the PR, ensuring developers receive contextual feedback without having to leave their version control system.
Each issue highlighted in the report is accompanied by an AI-generated suggestion for a fix. This allows you to not only understand the problem but also see a direct solution. If you agree with the recommendation, you can apply the change and commit the suggested fix directly from the PR comment with a single click, significantly speeding up the code review and remediation process.
Static Code Review
Typo automatically analyzes pull requests to detect security vulnerabilities, insecure coding patterns, and performance issues using a configurable rule engine.
The automatic code review helps you save time, streamline the review process, and improve code quality, making your team more productive.
All issues detected are categorized into five key areas:
These rule-based checks can be fully customized from Settings > Code health > Rules. You can also enable alerts for specific rules to stay informed about critical issues in real time.
Typo intelligently understands the context of your code to identify and fix issues with high accuracy. It helps you maintain clean, consistent, and secure code—reducing the risk of security breaches and improving long-term maintainability.
For each issue, Typo provides:
A clear description of the problem
An explanation of the bad practice
A recommended good practice to follow
This guidance ensures developers not only fix issues but also learn from them.
Real-time PR reviews
Typo automatically analyzes every pull request as soon as it’s raised, identifying issues and posting a detailed report directly as a comment on the PR. This ensures developers receive instant, actionable feedback without disrupting their workflow.
When a developer creates a pull request, Typo automatically initiates the analysis process using your configured rule set. It evaluates the code and posts a comment on the PR summarizing all detected issues, organized into clear categories for quick review. Clicking on the report takes you to a detailed view in Typo, where each issue is explained with a brief description, an example of the problematic code (Bad Practice), and a recommended fix (Good Practice). All issues are grouped into five key categories: OWASP Top 10, Security, Vulnerability, Performance, and Code Smell.
This integration enables developers to resolve issues faster, improve code quality, and significantly cut down on review and remediation time.
Supported Languages -
C#
CSS
CloudFormation
Docker
Flex
Go
HTML
Java
JavaScript
Kotlin
Kubernetes
PHP
Python
Ruby
Scala
Secrets
Terraform
Text
TypeScript
VB.NET
XML
AI Automated Code Fixes
Typo automatically suggests safe, functionally equivalent code changes for specific detected issues - helping you resolve problems faster and with confidence. Powered by AI, it streamlines your pull request process by quickly identifying and fixing issues, so you can push clean code without the stress in a single click.
AI-powered PR Summaries
Typo automatically generates summaries for each pull request, helping reviewers understand the purpose, scope, and code churn at a glance. These AI-powered summaries accelerate the review process by providing clear context before diving into the code.
Last updated