Spotbugs Alternatives - Java Code Analysis

Popularity

6.9

Growing

Activity

8.2

Declining

Stars 1,593

Watchers 67

Forks 248

Last Commit 8 days ago

Programming language: Java

Tags: Code Analysis

Latest version: v4.0.0._beta4

Spotbugs alternatives and similar libraries

Based on the "Code Analysis" category

Checkstyle

9.6 9.5 L3 Spotbugs VS Checkstyle

Static analysis of coding conventions and standards.
Infer

9.3 9.8 Spotbugs VS Infer

Tool to produce a list of potential bugs.
SonarQube

8.7 9.8 L3 Spotbugs VS SonarQube

Integrates other analysis components via plugins and provides an overview of the metrics over time.
Error Prone

8.5 9.4 L3 Spotbugs VS Error Prone

Catches common programming mistakes as compile-time errors.
PMD

7.9 9.8 L3 Spotbugs VS PMD

Source code analysis for finding bad coding practices.
NullAway

7.5 7.8 Spotbugs VS NullAway

Eliminates NullPointerExceptions with low build-time overhead.
SonarJava

5.9 9.3 Spotbugs VS SonarJava

Static analyzer for SonarQube & SonarLint.
Spoon

5.9 8.6 L2 Spotbugs VS Spoon

Library for analyzing and transforming Java source code.
FindBugs

5.4 0.0 L1 Spotbugs VS FindBugs

Static analysis of bytecode to find potential bugs.
jQAssistant

3.4 2.2 Spotbugs VS jQAssistant

Static code analysis with Neo4J-based query language.
Sourcetrail

2.6 5.5 Spotbugs VS Sourcetrail

Visual source code navigator.
Codacy

- - Spotbugs VS Codacy

Continuous static analysis, code coverage, and software metrics to automate code reviews.

* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.

Do you think we are missing an alternative of Spotbugs or a related project?

Add another 'Code Analysis' Library

Popular Comparisons

README

SpotBugs is the spiritual successor of FindBugs, carrying on from the point where it left off with support of its community.

SpotBugs is licensed under the GNU LESSER GENERAL PUBLIC LICENSE.

More information at the official website. A lot of things can still be found at the old FindBugs website.

Build

SpotBugs is built using Gradle. The recommended way to obtain it is to simply run the gradlew (or gradlew.bat) wrapper, which will automatically download and run the correct version as needed (using the settings in gradle/wrapper/gradle-wrapper.properties).

To see a list of build options, run gradle tasks (or gradlew tasks). The build task will perform a full build and test.

To build the SpotBugs plugin for Eclipse, you'll need to create the file eclipsePlugin/local.properties, containing a property eclipseRoot.dir that points to an Eclipse installation's root directory (see .travis.yml for an example), then run the build. To prepare Eclipse environment only, run ./gradlew eclipse. See also detailed steps.

Using SpotBugs

SpotBugs can be used standalone and through several integrations, including:

Questions?

You can contact us using our general purpose mailing list.

*Note that all licence references and agreements mentioned in the Spotbugs README section above are relevant to that project's source code only.

Spotbugs

Static analysis of bytecode to find potential bugs.