Displaying 1 to 20 from 42 results

Flow - A static type checker for JavaScript

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

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.

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.

jsinspect - Detect copy-pasted and structurally similar code

Detect copy-pasted and structurally similar JavaScript code. Requires Node.js 6.0+, and supports ES6, JSX as well as Flow. Note: the project has been mostly rewritten for the 0.10 release and saw several breaking changes.We've all had to deal with code smell, and duplicate code is a common source. While some instances are easy to spot, this type of searching is the perfect use-case for a helpful CLI tool.

gometalinter - Concurrently run Go lint tools and normalise their output

The number of tools for statically checking Go source for errors and warnings is impressive.eg.

gcvis - Visualise Go program GC trace data in real time

Visualise Go program GC trace data in real time

errcheck - errcheck checks that you checked errors.

errcheck is a program for checking for unchecked errors in go programs.errcheck requires Go 1.6 or newer and depends on the package go/loader from the golang.org/x/tools repository.

PMD - An extensible cross-language static code analyzer

PMD is a source code analyzer. It finds common programming flaws like unused variables, empty catch blocks, unnecessary object creation, and so forth. It supports Java, JavaScript, Salesforce.com Apex and Visualforce, PLSQL, Apache Velocity, XML, XSL.

EclEmma - Java Code Coverage for Eclipse

EclEmma is a free Java code coverage tool for Eclipse, available under the Eclipse Public License. It brings code coverage analysis directly into the Eclipse workbench. The EclEmma project is also the home of the JaCoCo code coverage library which is the technical back-end for EclEmma and also has integrations with many other build and software quality tools.

credo - A static code analysis tool for the Elixir language with a focus on code consistency and teaching

Credo is a static code analysis tool for the Elixir language with a focus on teaching and code consistency. It implements its own style guide.

Checkstyle - Checks Java coding standard

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.


StyleCop analyzes C# source code to enforce a set of style and consistency rules. It can be run from inside of Visual Studio or integrated into an MSBuild project.

SpotBugs - FindBugs' successor, A tool for static analysis to look for bugs in Java code.

SpotBugs is the spiritual successor of FindBugs, carrying on from the point where it left off with support of its community. SpotBugs is a program which uses static analysis to look for bugs in Java code.

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.

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.

patterns & practices: Visual Studio 2005 Team System Guidance

The purpose of this project is to build some insightful and practical guidance around using Visual Studio Team System 2005. It's a collaborative effort between patterns & practices, VSTS team members, and industry experts.