Software Alternatives & Reviews

FindBugs VS Checkstyle

Compare FindBugs VS Checkstyle and see what are their differences

FindBugs logo FindBugs

Findbugs is a tool that looks for bugs in Java code. Findbugs finds the bugs by analyzing computer software without actually executing programs. Using this software allows for easy debugging and repairing broken script. Read more about FindBugs.

Checkstyle logo Checkstyle

Checkstyle is a development tool to help programmers write Java code that adheres to a coding...
  • FindBugs Landing page
    Landing page //
    2019-01-11
  • Checkstyle Landing page
    Landing page //
    2023-07-29

FindBugs videos

Static Code Analysis With FindBugs: Step By Step Tutorial

Checkstyle videos

CheckStyle - A development tool for maintaining better Java coding standards for Application

More videos:

  • Review - CheckStyle || Maven || Configuration|| HTML Report - 1
  • Review - Install and Use CheckStyle for Java as an IntelliJ IDEA Plugin 2018

Category Popularity

0-100% (relative to FindBugs and Checkstyle)
Code Coverage
50 50%
50% 50
Code Analysis
47 47%
53% 53
Code Review
44 44%
56% 56
Code Quality
51 51%
49% 49

User comments

Share your experience with using FindBugs and Checkstyle. For example, how are they different and which one is better?
Log in or Post with

Reviews

These are some of the external sources and on-site user reviews we've used to compare FindBugs and Checkstyle

FindBugs Reviews

TOP 40 Static Code Analysis Tools (Best Source Code Analysis Tools)
A tool that helps in analyzing C/C++, Java, C#, RPG and Python codes. Another good thing about this tool is it allows integration with free static checker tools like cppcheck, PMD, FindBugs. Basic Version of this tool is free but it comes with fewer features. Based on the need, you can decide whether the free version satisfies the requirement or not.

Checkstyle Reviews

We have no reviews of Checkstyle yet.
Be the first one to post

Social recommendations and mentions

Based on our record, Checkstyle should be more popular than FindBugs. It has been mentiond 5 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

FindBugs mentions (3)

  • Scanning for flaws?
    The tools generally depend on the programming language. You might be looking for something like a "linter" or static analyzer (i.e. FindBugs for Java). Source: over 2 years ago
  • Why we need multiple code analysis tools?
    These tools perform analysis on the application's source code without executing/running the code on a platform. In other words, a bot goes line by line of source code to find any bug defined by preconfigured policies/rules. It could be compared to manual code review, but the review is done by a bot. Mostly, code quality, coding standard aspects are targeted to be scanned. The biggest name in static code analysis... - Source: dev.to / over 2 years ago
  • Review of Java Static Analysis Tools
    FindBugs looks for bugs in Java Code, and this means over 400 different bugs. - Source: dev.to / about 3 years ago

Checkstyle mentions (5)

  • Custom Gradle Plugin for Unified Static Code Analysis
    PMD and Checkstyle are static analysis tools that check your code on each project build. Gradle allows to apply them easily. - Source: dev.to / about 1 year ago
  • java checkstyle in neovim?
    AFAIK, you can't use it with nvim-jdtls, but here you shave a list of checkstyle plugins and there are a Gradle and a Maven one that your could use. Source: over 1 year ago
  • Spring Boot – Black Box Testing
    The generated classes should be put into .gitignore. Otherwise, if you have Checkstyle, PMD, or SonarQube in your project, then generated classes can violate some rules. Besides, if you don't put them into .gitignore, then each pull request might become huge due to the fact that even a slightest fix can lead to lots of changes in the generated classes. - Source: dev.to / over 1 year ago
  • Basics of CI/CD
    Speaking of code style there aren't many differences. You can try Checkstyle plugin. It automatically fails a build that violates any of the stated requirements. For example, the code might have an unused import. Besides you can look at cloud services that run the code analysis and shows the result as a bunch of charts (SonarCloud can also do that). - Source: dev.to / over 2 years ago
  • Design an Effective Build Stage for Continuous Integration
    Java developers use powerful IDEs that lint code in realtime. Powerful as they are, they are not enough. Quality checks must also be part of the CI pipeline. We can use checkstyle to add a linting job. - Source: dev.to / about 3 years ago

What are some alternatives?

When comparing FindBugs and Checkstyle, you can also consider the following products

SonarQube - SonarQube, a core component of the Sonar solution, is an open source, self-managed tool that systematically helps developers and organizations deliver Clean Code.

Pmd - PMD scans Java source code and looks for potential problems like:

Checkmarx - The industry’s most comprehensive AppSec platform, Checkmarx One is fast, accurate, and accelerates your business.

Codacy - Automatically reviews code style, security, duplication, complexity, and coverage on every change while tracking code quality throughout your sprints.

ReSharper - ReSharper is a productivity tool for visual studio that provides tools and features to help you manage your code.

CodeClimate - Code Climate provides automated code review for your apps, letting you fix quality and security issues before they hit production. We check every commit, branch and pull request for changes in quality and potential vulnerabilities.