Alternatives to FindBugs logo

Alternatives to FindBugs

PMD, Checkstyle , SonarLint, SonarQube, and CodeNarc are the most popular alternatives and competitors to FindBugs.
118
81
+ 1
0

What is FindBugs and what are its top alternatives?

It detects possible bugs in Java programs. Potential errors are classified in four ranks: scariest, scary, troubling and of concern. This is a hint to the developer about their possible impact or severity.
FindBugs is a tool in the Code Review category of a tech stack.

Top Alternatives to FindBugs

  • PMD

    PMD

    It is a source code analyzer. It finds common programming flaws like unused variables, empty catch blocks, unnecessary object creation, and so forth. It includes CPD, the copy-paste-detector. ...

  • Checkstyle

    Checkstyle

    It is a development tool to help programmers write Java code that adheres to a coding standard. It automates the process of checking Java code to spare humans of this boring (but important) task. This makes it ideal for projects that want to enforce a coding standard. ...

  • SonarLint

    SonarLint

    It is an IDE extension that helps you detect and fix quality issues as you write code. Like a spell checker, it squiggles flaws so that they can be fixed before committing code. ...

  • SonarQube

    SonarQube

    SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving. ...

  • CodeNarc

    CodeNarc

    A flexible framework for rules, rule sets and custom rules means it's easy to configure it to fit into your project. Build tool, framework support, and report generation are all enterprise ready. ...

  • ESLint

    ESLint

    A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease. ...

  • Prettier

    Prettier

    Prettier is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary. ...

  • TSLint

    TSLint

    An extensible static analysis tool that checks TypeScript code for readability, maintainability, and functionality errors. It is widely supported across modern editors & build systems and can be customized with your own lint rules, configurations, and formatters. ...

FindBugs alternatives & related posts

PMD logo

PMD

32
72
0
An extensible cross-language static code analyzer
32
72
+ 1
0
PROS OF PMD
    Be the first to leave a pro
    CONS OF PMD
      Be the first to leave a con

      related PMD posts

      Joshua Dean Küpper
      CEO at Scrayos UG (haftungsbeschränkt) · | 1 upvote · 274.7K views

      We use PMD alongside Checkstyle and FindBugs (Spotbugs) for our static code analysis, as a standard stage in all of our pipelines. PMD offers us insight into various optimization possibilities, best-practice alignment, coding convention compliance and general problems with our code.

      See more
      Checkstyle  logo

      Checkstyle

      73
      77
      0
      A static code analysis tool
      73
      77
      + 1
      0
      PROS OF CHECKSTYLE
        Be the first to leave a pro
        CONS OF CHECKSTYLE
          Be the first to leave a con

          related Checkstyle posts

          Joshua Dean Küpper
          CEO at Scrayos UG (haftungsbeschränkt) · | 1 upvote · 274.7K views

          We use PMD alongside Checkstyle and FindBugs (Spotbugs) for our static code analysis, as a standard stage in all of our pipelines. PMD offers us insight into various optimization possibilities, best-practice alignment, coding convention compliance and general problems with our code.

          See more
          SonarLint logo

          SonarLint

          114
          220
          10
          An IDE extension to detect and fix issues as you write code
          114
          220
          + 1
          10
          PROS OF SONARLINT
          • 10
            IDE Integration
          CONS OF SONARLINT
          • 2
            Not Very User Friendly
          • 2
            Non contextual warnings

          related SonarLint posts

          SonarQube logo

          SonarQube

          1.3K
          1.4K
          39
          Continuous Code Quality
          1.3K
          1.4K
          + 1
          39
          PROS OF SONARQUBE
          • 20
            Tracks code complexity and smell trends
          • 12
            IDE Integration
          • 7
            Complete code Review
          CONS OF SONARQUBE
          • 5
            Sales process is long and unfriendly
          • 4
            Paid support is poor, techs arrogant and unhelpful

          related SonarQube posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.3M views

          Our whole DevOps stack consists of the following tools:

          • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
          • Respectively Git as revision control system
          • SourceTree as Git GUI
          • Visual Studio Code as IDE
          • CircleCI for continuous integration (automatize development process)
          • Prettier / TSLint / ESLint as code linter
          • SonarQube as quality gate
          • Docker as container management (incl. Docker Compose for multi-container application management)
          • VirtualBox for operating system simulation tests
          • Kubernetes as cluster management for docker containers
          • Heroku for deploying in test environments
          • nginx as web server (preferably used as facade server in production environment)
          • SSLMate (using OpenSSL) for certificate management
          • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
          • PostgreSQL as preferred database system
          • Redis as preferred in-memory database/store (great for caching)

          The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

          • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
          • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
          • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
          • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
          • Scalability: All-in-one framework for distributed systems.
          • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
          See more
          Ganesa Vijayakumar
          Full Stack Coder | Module Lead · | 19 upvotes · 2.5M views

          I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

          I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

          As per my work experience and knowledge, I have chosen the followings stacks to this mission.

          UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

          Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

          Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

          Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

          Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

          Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

          Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

          Happy Coding! Suggestions are welcome! :)

          Thanks, Ganesa

          See more
          CodeNarc logo

          CodeNarc

          7
          9
          0
          Analyzes Groovy code for defects
          7
          9
          + 1
          0
          PROS OF CODENARC
            Be the first to leave a pro
            CONS OF CODENARC
              Be the first to leave a con

              related CodeNarc posts

              ESLint logo

              ESLint

              15.3K
              8.6K
              23
              The fully pluggable JavaScript code quality tool
              15.3K
              8.6K
              + 1
              23
              PROS OF ESLINT
              • 7
                Consistent javascript - opinions don't matter anymore
              • 5
                IDE Integration
              • 4
                Free
              • 3
                Customizable
              • 2
                Focuses code review on quality not style
              • 2
                Broad ecosystem of support & users
              CONS OF ESLINT
                Be the first to leave a con

                related ESLint posts

                Simon Reymann
                Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.3M views

                Our whole DevOps stack consists of the following tools:

                • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
                • Respectively Git as revision control system
                • SourceTree as Git GUI
                • Visual Studio Code as IDE
                • CircleCI for continuous integration (automatize development process)
                • Prettier / TSLint / ESLint as code linter
                • SonarQube as quality gate
                • Docker as container management (incl. Docker Compose for multi-container application management)
                • VirtualBox for operating system simulation tests
                • Kubernetes as cluster management for docker containers
                • Heroku for deploying in test environments
                • nginx as web server (preferably used as facade server in production environment)
                • SSLMate (using OpenSSL) for certificate management
                • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
                • PostgreSQL as preferred database system
                • Redis as preferred in-memory database/store (great for caching)

                The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

                • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
                • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
                • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
                • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
                • Scalability: All-in-one framework for distributed systems.
                • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
                See more
                Simon Reymann
                Senior Fullstack Developer at QUANTUSflow Software GmbH · | 20 upvotes · 797.3K views

                Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

                • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
                • Vue Styleguidist as our style guide and pool of developed Vue.js components
                • Vuetify as Material Component Framework (for fast app development)
                • TypeScript as programming language
                • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
                • ESLint, TSLint and Prettier for coding style and code analyzes
                • Jest as testing framework
                • Google Fonts and Font Awesome for typography and icon toolkit
                • NativeScript-Vue for mobile development

                The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

                • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
                • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
                • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
                • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
                • Large scaling. Vue.js can help to develop pretty large reusable templates.
                • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
                See more
                Prettier logo

                Prettier

                2.4K
                445
                7
                Prettier is an opinionated code formatter.
                2.4K
                445
                + 1
                7
                PROS OF PRETTIER
                • 2
                  Customizable
                • 1
                  Atom/VSCode package
                • 1
                  Follows the Ruby Style Guide by default
                • 1
                  Runs offline
                • 1
                  Completely free
                • 1
                  Open Source
                CONS OF PRETTIER
                  Be the first to leave a con

                  related Prettier posts

                  Simon Reymann
                  Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.3M views

                  Our whole DevOps stack consists of the following tools:

                  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
                  • Respectively Git as revision control system
                  • SourceTree as Git GUI
                  • Visual Studio Code as IDE
                  • CircleCI for continuous integration (automatize development process)
                  • Prettier / TSLint / ESLint as code linter
                  • SonarQube as quality gate
                  • Docker as container management (incl. Docker Compose for multi-container application management)
                  • VirtualBox for operating system simulation tests
                  • Kubernetes as cluster management for docker containers
                  • Heroku for deploying in test environments
                  • nginx as web server (preferably used as facade server in production environment)
                  • SSLMate (using OpenSSL) for certificate management
                  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
                  • PostgreSQL as preferred database system
                  • Redis as preferred in-memory database/store (great for caching)

                  The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

                  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
                  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
                  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
                  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
                  • Scalability: All-in-one framework for distributed systems.
                  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
                  See more
                  Simon Reymann
                  Senior Fullstack Developer at QUANTUSflow Software GmbH · | 20 upvotes · 797.3K views

                  Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

                  • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
                  • Vue Styleguidist as our style guide and pool of developed Vue.js components
                  • Vuetify as Material Component Framework (for fast app development)
                  • TypeScript as programming language
                  • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
                  • ESLint, TSLint and Prettier for coding style and code analyzes
                  • Jest as testing framework
                  • Google Fonts and Font Awesome for typography and icon toolkit
                  • NativeScript-Vue for mobile development

                  The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

                  • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
                  • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
                  • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
                  • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
                  • Large scaling. Vue.js can help to develop pretty large reusable templates.
                  • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
                  See more
                  TSLint logo

                  TSLint

                  905
                  189
                  0
                  An extensible linter for the TypeScript language
                  905
                  189
                  + 1
                  0
                  PROS OF TSLINT
                    Be the first to leave a pro
                    CONS OF TSLINT
                      Be the first to leave a con

                      related TSLint posts

                      Simon Reymann
                      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.3M views

                      Our whole DevOps stack consists of the following tools:

                      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
                      • Respectively Git as revision control system
                      • SourceTree as Git GUI
                      • Visual Studio Code as IDE
                      • CircleCI for continuous integration (automatize development process)
                      • Prettier / TSLint / ESLint as code linter
                      • SonarQube as quality gate
                      • Docker as container management (incl. Docker Compose for multi-container application management)
                      • VirtualBox for operating system simulation tests
                      • Kubernetes as cluster management for docker containers
                      • Heroku for deploying in test environments
                      • nginx as web server (preferably used as facade server in production environment)
                      • SSLMate (using OpenSSL) for certificate management
                      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
                      • PostgreSQL as preferred database system
                      • Redis as preferred in-memory database/store (great for caching)

                      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

                      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
                      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
                      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
                      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
                      • Scalability: All-in-one framework for distributed systems.
                      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
                      See more
                      Simon Reymann
                      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 20 upvotes · 797.3K views

                      Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

                      • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
                      • Vue Styleguidist as our style guide and pool of developed Vue.js components
                      • Vuetify as Material Component Framework (for fast app development)
                      • TypeScript as programming language
                      • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
                      • ESLint, TSLint and Prettier for coding style and code analyzes
                      • Jest as testing framework
                      • Google Fonts and Font Awesome for typography and icon toolkit
                      • NativeScript-Vue for mobile development

                      The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

                      • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
                      • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
                      • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
                      • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
                      • Large scaling. Vue.js can help to develop pretty large reusable templates.
                      • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
                      See more