CodeFactor

CodeFactor is a hosted automated code review and static analysis service for GitHub and Bitbucket repos, priced per private repository with unlimited users.

CodeFactor checks every commit and pull request in a GitHub or Bitbucket repository and reports the code quality issues it finds, so problems surface before a change merges. It is a hosted service run by Adroiti Technologies, which operates it under the CodeFactor name. Each connected project gets a code quality grade from A to F alongside counts of its open issues. The analysis runs on established open source engines, each reading the repository's own configuration file. ESLint and Stylelint cover web code, RuboCop covers Ruby, Pylint and pycodestyle cover Python, and Checkstyle covers Java. Supported languages run from Python, TypeScript and C# to Go, Kotlin, Swift and Haskell. The project overview shows recent commits and the most problematic files, while the technical debt view puts the most critical issues first by issue size, change frequency and file size. Pull request integration posts a commit status on GitHub and Bitbucket, and with GitHub Checks enabled the findings appear as code comments inside the pull request. Code Autofix corrects some findings on demand or automatically by opening a new pull request or commit, and an optional Duplication checker finds similar or duplicate code. CodeFactor suits development teams that keep their code on GitHub or Bitbucket and want lint and static analysis on every change without hosting an analysis server. Open source maintainers can connect public projects and show contributors where the codebase stands. Teams that already maintain ESLint, RuboCop or Pylint settings get those same rules applied to every pull request. Plans are sized by the number of private repositories rather than by seat, so a team adds developers without changing what it buys. A typical setup connects a repository, lets the first analysis grade it, and then works through the technical debt list file by file. On each pull request, the CodeFactor status on GitHub or Bitbucket settles style and lint questions before a reviewer reads the logic. Teams moving a legacy codebase toward a stricter ESLint or RuboCop setup use Code Autofix to clear the mechanical fixes in a single pull request. Inspection can be switched on for the branches that matter and left off for experiments. The fit is strongest for a team that wants the linters it already trusts run the same way on every branch and every pull request.