Checkstyle - Checks Java coding standard

  •        5243

Checkstyle is a tool to help programmers write Java code that adheres to a coding standard. Checkstyle is highly configurable and can be made to support almost any coding standard. Checkstyle provides checks that find class design problems, duplicate code, or bug patterns like double checked locking. This tool could be integrated as Ant task.

Plugins are available for Eclipse, Netbeans, QALab, Emacs etc.

http://checkstyle.sourceforge.net/

Tags
Implementation
License
Platform

   




Related Projects

CodeNarc - Static Analysis for Groovy


CodeNarc analyzes Groovy code for defects, bad practices, inconsistencies, style issues, coding standards, best practices and more. CodeNarc triggers violations based on rules which are predefined or custom rules. The static analysis report is generated in XML or HTML format. It is well integrated with the Ant Task and plugins exist for Maven, Gradle, Grails, Griffon, Sonar and Hudson.

JSHint - A Static Code Analysis Tool for JavaScript


JSHint is a community-driven tool to detect errors in JavaScript code and enforce your team's coding conventions.

FindBugs - Static Analysis Tool for Java


FindBugs uses static analysis to look for bugs in Java code. it can analyze programs compiled for any version of Java. Eclipse and Maven plugins are available. FindBugs has been downloaded more than 700,000 times.

scapegoat - Scala compiler plugin for static code analysis


Scapegoat is a Scala static code analyzer, what is more colloquially known as a code lint tool or linter. Scapegoat works in a similar vein to Java's FindBugs or checkstyle, or Scala's Scalastyle.A static code analyzer is a tool that flag suspicious language usage in code. This can include behavior likely to lead or bugs, non idiomatic usage of a language, or just code that doesn't conform to specified style guidelines.

checkstyle - Java source code static analysis


Java source code static analysis



JLint - static analysis for Java


Jlint will check your Java code and find bugs, inconsistencies and synchronization problems by doing data flow analysis and building the lock graph. Jlint is extremely fast. It is easy to learn and requires no changes to the class files. Jlint has been used in an industrial environment and successfully uncovered faults with little effort.

goreporter - A Golang tool that does static analysis, unit testing, code review and generate code quality report


Install goreporter (see above).You have to confirm that your project is operational. In particular, the problem with vendor, when the package is not found in the default path, goreporter will look again from the possible vendor path.

Codelyzer - Static analysis for Angular projects.


A set of tslint rules for static code analysis of Angular TypeScript projects.You can run the static code analyzer over web apps, NativeScript, Ionic, etc.

Flow - A static type checker for JavaScript


Adds static typing to JavaScript to improve developer productivity and code quality.

NullAway - A tool to help eliminate NullPointerExceptions (NPEs) in your Java code.


NullAway is a tool to help eliminate NullPointerExceptions (NPEs) in your Java code. To use NullAway, first add @Nullable annotations in your code wherever a field, method parameter, or return value may be null. Given these annotations, NullAway performs a series of type-based, local checks to ensure that any pointer that gets dereferenced in your code cannot be null. NullAway is similar to the type-based nullability checking in the Kotlin and Swift languages, and the Checker Framework and Eradicate null checkers for Java.NullAway is fast. It is built as a plugin to Error Prone and can run on every single build of your code. In our measurements, the build-time overhead of running NullAway is usually less than 10%. NullAway is also practical: it does not prevent all possible NPEs in your code, but it catches most of the NPEs we have observed in production while imposing a reasonable annotation burden, giving a great "bang for your buck." At Uber, we combine NullAway with RAVE to obtain thorough protection against NPEs in our Android apps.

SPDisposeCheck Static Code Analysis Ruleset for Visual Studio 2012


SPDisposeCheck Static Code Analysis Ruleset allows SharePoint 2010 developers to ensure SharePoint APIs are properly disposed using Visual Studio 2012.

Resource-Static-Analysis - The Resource Static Analysis enables companies and localization suppliers to quickly add scalable validation checks to help ensure quality doesn't suffer as software and content is localized and data is exchanged between internal workflows and even between companies


#Resource Static Analysis The Resource Static Analysis enables companies and localization suppliers to quickly add scalable validation checks to help ensure quality doesn't suffer as software and content is localized and data is exchanged between internal workflows and even between companies. The analysis engine is already in use by multiple teams at Microsoft, including Windows (WDG), Office (ASG), and Azure+SQL+VS (C&E).This project also includes a complete sample that the Microsoft Office team is using to validate that sufficient resource context has been added by the developers in Word, Excel, OneNote, etc.. Validating the context ensures that those resources can be efficiently localized appropriately.

Panopticode - Gathers, Correlats, and displays code metrics


The Panopticode project provides a set of open source tools for gathering, correlating, and displaying code metrics. It evaluates software quality and ensures coding standards. It installs and configures set of tools like Emma or Cobertura for unit test code coverage, Checkstyle to validate the coding standards, JDepend to check the dependency, JavaNCSS for Cyclomatic Complexity metrics.

JSLint - The JavaScript Code Quality Tool


JSLint is a JavaScript program that looks for problems in JavaScript programs. It is a code quality tool. JSLint takes a JavaScript source and scans it. If it finds a problem, it returns a message describing the problem and an approximate location within the source. The problem is not necessarily a syntax error, although it often is. JSLint looks at some style conventions as well as structural problems. It does not prove that your program is correct.

Bruno - Static code analysis application. Scans code for vulnerabilities.


Static code analysis application. Scans code for vulnerabilities.

Infer - A static analyzer for Java, C and Objective-C


A static analyzer for Java, C and Objective-C. It is a tool to detect bugs in Android and iOS apps.

go-tools - A collection of tools and libraries for working with Go code, including linters and static analysis


honnef.co/go/tools/... is a collection of tools and libraries for working with Go code, including linters and static analysis.These tools are supported by patrons on Patreon and sponsors. If you use these tools at your company, consider purchasing commercial support.

codecoroner - tool for detecting unused functions and variables in Go source code


Leaving dead code in a large codebase with multiple libraries is difficult to avoid.Things get moved around; functions get refactored, leaving helpers on their own; people miscommunicate. One of the easiest ways to detect dead code is through static analysis. Unfortunately, Go's current static analysis tools (the oracle) do not make aggregation of unused functions as easy as it should be.This tool, go-unused-funcs, uses the output of the Go oracle library to find unused functions/methods in your

js-code-analyzer - Static JS-code analysis using JSLint and Esprima.


Static JS-code analysis using JSLint and Esprima.