List of tools for static code analysis

This is a list of tools for static code analysis.

Language

Multi-language

• Axivion Bauhaus Suite – A static code analysis tool suite for Ada, C, C++, C#, and Java code that performs various analyses such as architecture checking, interface analyses, MISRA checking, and clone detection.
• BlueOptima – Coding Effort Analytics objectively measure the productivity of software developers by evaluating the deltas in static source code metrics between commits. ART (Analysis of Relative Thresholds) generates rules using these same static metrics to ensure the maintainability and stability of a code base.
• CAST Application Intelligence Platform – Detailed, audience-specific dashboards to measure quality and productivity. Cross-tier, cross-technology analysis of 50+ languages, C, C++, Java, .NET, Oracle, PeopleSoft, SAP, Siebel, Spring, Struts, Hibernate and all major databases.
• Cigital SecureAssist - A lightweight IDE plugin that points out common security vulnerabilities in real time as the developer is coding. Supports Java, .NET, and PHP.
• Codacy - Static analysis and automated code reviews for Python, Ruby, PHP, Java, JavaScript, Scala, and more. Provides code metrics on code security, duplication, complexity, style, and coverage.
• Compuware Topaz for Program Analysis – A static code analysis for PL/I and COBOL. Produces visual displays of structure charts and logic/data flow and shows dependencies across programs.
• ConQAT – Continuous quality assessment toolkit that allows flexible configuration of quality analyses (architecture conformance, clone detection, quality metrics, etc.) and dashboards. Supports Java, C#, C++, JavaScript, ABAP, Ada and many other languages.
• Coverity – A static analysis tool for C, C++, C#, Objective-C, Java, Javascript, node.JS, Ruby, PHP, & Python.
• HP Fortify Software Static Code Analyzer – Helps developers identify software security vulnerabilities in C, C++, Java, JSP, .NET, ASP.NET, classic Active Server Pages (ASP), ColdFusion, PHP, Visual Basic 6, VBScript, JavaScript, PL/SQL, T-SQL, Python, Objective-C and COBOL and configuration files.
• GrammaTech CodeSonar – Defect detection (buffer overruns, memory leaks, etc.), concurrency and security checks, architecture visualization and software metrics for C, C++, and Java source code.
• IBM Security AppScan (formally known as IBM Rational AppScan) Source Edition – Analyzes source code to identify security vulnerabilities while integrating security testing with software development processes and systems. Supports C, C++, .NET, Java, JSP, JavaScript, ColdFusion, Classic ASP, PHP, Perl, Visual Basic 6, PL/SQL, T-SQL, and COBOL
• Imagix 4D – Identifies problems in variable use, task interaction and concurrency, especially in embedded applications, as part of an overall system for understanding, improving and documenting C, C++ and Java code.
• Kiuwan – Software Analytics end-to-end platform for static analysis, defect detection, application security & IT Risk Management, with enhanced life cycle and application governance features. It supports over 25 languages, including Objective-C, Java, JSP, JavaScript, PHP, C, C++, ABAP, COBOL, JCL, C#, PL/SQL, Transact-SQL, SQL, Visual Basic, Visual Basic .NET, Android (operating system).
• Klocwork – Provides security vulnerability, standards compliance (MISRA, ISO 26262 and others), defect detection and build-over-build trend analysis for C, C++, C# and Java.
• LDRA Testbed – A software analysis and testing tool suite for C, C++, Ada83, Ada95 and Assembler (Intel, Freescale, Texas Instruments).
• MALPAS – A software static analysis toolset for a variety of languages including Ada, C, Pascal and Assembler (Intel, PowerPC and Motorola). Used primarily for safety critical applications in Nuclear and Aerospace industries.
• Moose – Moose started as a software analysis platform with many tools to manipulate, assess or visualize software. It can evolve to a more generic data analysis platform. Supported languages are C, C++, Java, Smalltalk, .NET, more may be added.
• Parasoft – Provides static analysis (pattern-based, flow-based, in-line, metrics) for C, C++, Java, .NET (C#, VB.NET, etc.), JSP, JavaScript, XML, and other languages. Through a Development Testing Platform, static code analysis functionality is integrated with unit testing, peer code review, runtime error detection and traceability.
• Copy/Paste Detector (CPD) – PMDs duplicate code detection for (e.g.) Java, JSP, C, C++, ColdFusion, PHP and JavaScript^[1] code.
• Polyspace – Uses abstract interpretation to detect and prove the absence of certain run time errors in source code for C, C++, and Ada
• Pretty Diff - A language-specific code comparison tool that features language-specific analysis reporting in addition to language-specific minification and beautification algorithms.
• Protecode – Analyzes the composition of software source code and binary files, searches for open source and third party code and their associated licensing obligations. Can also detect security vulnerabilities.
• PVS-Studio – A software analysis tool for C, C++, C++11, C++/CX (Component Extensions), C#.
• Rogue Wave Software OpenLogic – Scans source code and binaries to identify open source code and licenses, manages open source policies and approvals, reports security vulnerabilities, and provides open source technical support.
• Semmle – Supports C, C++, C#, Java, JavaScript, Objective-C, Python and Scala.
• SofCheck Inspector – Static detection of logic errors, race conditions, and redundant code for Ada and Java; automatically extracts pre-postconditions from code.
• SonarQube – A continuous inspection engine to manage the technical debt: unit tests, complexity, duplication, design, comments, coding standards and potential problems. Supports languages: ABAP, Android (Java), C, C++, CSS, Objective-C, COBOL, C#, Flex, Forms, Groovy, Java, JavaScript, Natural, PHP, PL/SQL, Swift, Visual Basic 6, Web, XML, Python.
• Sotoarc-Sotograph – Architecture and quality in-depth analysis and monitoring for C, C++, C#, Java, ABAP.
• SourceMeter - A platform-independent, command-line static source code analyzer for Java, C, C++, RPG IV (AS/400) and Python.
• SQuORE is a multi-purpose and multi-language monitoring tool^[2] for software projects.
• Understand – A multi-platform tool for code analysis and comprehension of large code bases. Supported languages include Ada, Cobol, Ansi C, K&R C, Ansi C++, C#, FORTRAN, Java, Jovial, Pascal, PL/M, Python, VHDL, Objective C, Objective C++, HTML, PHP, JavaScript, and XML.
• Veracode – Finds security flaws in application binaries and bytecode without requiring source. Supported languages include C, C++, .NET (C#, C++/CLI, VB.NET, ASP.NET), Java, JSP, ColdFusion, PHP, Ruby on Rails, JavaScript (including Node.js), Objective-C, Active Server Pages, Visual Basic 6, and COBOL, including mobile applications on the Windows Mobile, BlackBerry, Android, and iOS platforms and written in JavaScript cross platform frameworks.^[3]
• Yasca – Yet Another Source Code Analyzer, a plugin-based framework to scan arbitrary file types, with plugins for C, C++, Java, JavaScript, ASP, PHP, HTML-CSS, ColdFusion, COBOL, and other file types. It integrates with other scanners, including FindBugs, PMD, and Pixy.

.NET

• .NET Compiler Platform (Codename Roslyn) – Open-source compiler framework for C# and Visual Basic .NET developed by Microsoft .NET. Provides an API for analyzing and manipulating syntax.
• CodeIt.Right – Combines static code analysis and automatic refactoring to best practices which allows automatic correction of code errors and violations; supports C# and VB.NET.
• CodeRush – A plugin for Visual Studio which alerts users to violations of best practices.
• FxCop – Free static analysis for Microsoft .NET programs that compiles to CIL. Standalone and integrated in some Microsoft Visual Studio editions; by Microsoft.
• NDepend – Simplifies managing a complex .NET code base by analyzing and visualizing code dependencies, by defining design rules, by doing impact analysis, and by comparing different versions of the code. Integrates into Visual Studio.
• Parasoft dotTEST – A static analysis, unit testing, and code review plugin for Visual Studio; works with languages for Microsoft .NET Framework and .NET Compact Framework, including C#, VB.NET, ASP.NET and Managed C++.
• StyleCop – Analyzes C# source code to enforce a set of style and consistency rules. It can be run from inside of Microsoft Visual Studio or integrated into an MSBuild project.

Ada

• SPARK Toolset - Verification tools for SPARK 2014 – a subset of Ada 2012 that leverages Ada's support for contracts. Designed to offer soundness, depth, modularity and efficiency of verification.
• AdaControl – A tool to control occurrences of various entities or programming patterns in Ada code, used for checking coding standards, enforcement of safety related rules, and support for various manual inspections.
• CodePeer – An advanced static analysis tool that detects potential run-time logic errors in Ada programs.
• Fluctuat – Abstract interpreter for the validation of numerical properties of programs.
• LDRA Testbed – A software analysis and testing tool suite for Ada83/95.
• Polyspace – Uses abstract interpretation to detect and prove the absence of certain run time errors in source code.
• SofCheck Inspector – (Bought by AdaCore) Static detection of logic errors, race conditions, and redundant code for Ada; automatically extracts pre-postconditions from code.

C, C++

• Astrée – finds all potential runtime errors and data races by abstract interpretation, can prove their absence, and can prove functional assertions; tailored towards safety-critical C code (e.g. avionics and automotive). Includes MISRA checker.
• Axivion Bauhaus Suite – A static code analysis tool suite that performs various analyses such as architecture checking, interface analyses, MISRA checking, and clone detection.
• BLAST – (Berkeley Lazy Abstraction Software verification Tool) – An open-source software model checker for C programs based on lazy abstraction (follow-on project is CPAchecker.^[4]).
• Cppcheck – Open-source tool that checks for several types of errors, including use of STL.
• cpplint – An open-source tool that checks for compliance with Google's style guide for C++ coding.
• Clang – An open-source compiler that includes a static analyzer.
• Coccinelle – An open-source source code pattern matching and transformation.
• Coverity – A static analysis tool for C/C++.
• Cppdepend – Simplifies managing a complex C/C++ code base by analyzing and visualizing code dependencies, by defining design rules, by doing impact analysis, and comparing different versions of the code.
• ECLAIR – A platform for the automatic analysis, verification, testing and transformation of C and C++ programs.
• Eclipse (software) – An open-source IDE that includes a static code analyzer.
• Fluctuat – Abstract interpreter for the validation of numerical properties of programs.
• Frama-C – An open-source static analysis framework for C.
• Goanna – A software analysis tool for C/C++.
• Klocwork Static Code Analysis – A static analysis tool for C/C++.
• Lint – The original static code analyzer for C.
• LDRA Testbed – A software analysis and testing tool suite for C/C++.
• Parasoft C/C++test – A C/C++ tool that does static analysis, unit testing, code review, and runtime error detection; plugins available for Visual Studio and Eclipse-based IDEs.
• PC-Lint – A software analysis tool for C/C++.
• Polyspace – Uses abstract interpretation to detect and prove the absence of run time errors, Dead Code in source code as well as used to check all MISRA (2004, 2012) rules (directives, non directives).
• PRQA QA·C and QA·C++ – Deep static analysis of C/C++ for quality assurance and guideline/coding standard enforcement with MISRA support.
• SLAM project – a project of Microsoft Research for checking that software satisfies critical behavioral properties of the interfaces it uses.
• Sparse – An open-source tool designed to find faults in the Linux kernel.
• Splint – An open-source evolved version of Lint, for C.

Java

JavaScript

• Google's Closure Compiler – JavaScript optimizer that rewrites code to be faster and smaller, and checks use of native JavaScript functions.
• JSHint – A community driven fork of JSLint.
• JSLint – JavaScript syntax checker and validator.

Objective-C, Objective-C++

• Clang – The free Clang project includes a static analyzer. As of version 3.2, this analyzer is included in Xcode.^[6]

Opa

• Opa includes its own static analyzer. As the language is intended for web application development, the strongly statically typed compiler checks the validity of high-level types for web data, and prevents by default many vulnerabilities such as XSS attacks and database code injections.

Packaging

• Lintian – Checks Debian software packages for common inconsistencies and errors.
• Rpmlint – Checks for common problems in rpm packages.

Perl

• Perl::Critic – A tool to help enforce common Perl best practices. Most best practices are based on Damian Conway's Perl Best Practices book.
• PerlTidy – Program that acts as a syntax checker and tester/enforcer for coding practices in Perl.
• Padre – An IDE for Perl that also provides static code analysis to check for common beginner errors.

PHP

• RIPS – A static code analyzer and audit framework for vulnerabilities in PHP applications.

PL/SQL

• TOAD - A PL/SQL development environment with a Code xPert component that reports on general code efficiency as well as specific programming issues.

Python

• Pylint – Static code analyzer. Quite stringent; includes many stylistic warnings as well.
• PyCharm – Cross-platform Python IDE with code inspections available for analyzing code on-the-fly in the editor and bulk analysis of the whole project.

Formal methods tools

Tools that use sound, i.e. no false negatives, formal methods approach to static analysis (e.g., using static program assertions):

• Astrée – finds all potential runtime errors by abstract interpretation, can prove the absence of runtime errors and can prove functional assertions; tailored towards safety-critical C code (e.g. avionics).
• CodePeer – Statically determines and documents pre- and post-conditions for Ada subprograms; statically checks preconditions at all call sites.
• ECLAIR – Uses formal methods-based static code analysis techniques such as abstract interpretation and model checking combined with constraint satisfaction techniques to detect or prove the absence of certain run time errors in source code.
• ESC/Java and ESC/Java2 – Based on Java Modeling Language, an enriched version of Java.
• Frama-C – An open-source static analysis framework for C.
• KeY – analysis platform for Java based on theorem proving with specifications in the Java Modeling Language; can generate test cases as counterexamples; stand-alone GUI or Eclipse integration
• MALPAS – A formal methods tool that uses directed graphs and regular algebra to prove that software under analysis correctly meets its mathematical specification.
• Polyspace – Uses abstract interpretation, a formal methods based technique,^[7] to detect and prove the absence of certain run time errors in source code for C/C++, and Ada
• SPARK Toolset including the SPARK Examiner – Based on the SPARK language, a subset of Ada.

See also

• Automated code review
• Best Coding Practices
• Dynamic code analysis
• Software metrics
• Integrated development environment (IDE) and Comparison of integrated development environments. IDEs will usually come with built-in support for static code analysis, or with an option to integrate such support. Eclipse offers such integration mechanism for most different types of extensions (plug-ins).

References

External links

• The Web Application Security Consortium's Static Code Analysis Tool List
• Java Static Checkers at DMOZ
• List of Java static code analysis plugins for Eclipse
• List of static source code analysis tools for C
• SAMATE-Source Code Security Analyzers
• SATE – Static Analysis Tool Exposition
• "A Comparison of Bug Finding Tools for Java", by Nick Rutar, Christian Almazan, and Jeff Foster, University of Maryland. Compares Bandera, ESC/Java 2, FindBugs, JLint, and PMD.
• "Mini-review of Java Bug Finders", by Rick Jelliffe, O'Reilly Media.