Code Analysis tools
CodeChecker can execute the following static analyzer tools:
We have created a separate converter tool which can be used to convert the output of different source code analyzer tools to a CodeChecker result directory which can be stored to a CodeChecker server.
Language | Analyzer | Support storage of analyzer results |
---|---|---|
C/C++ | Clang Tidy | ✓ |
Clang Static Analyzer | ✓ | |
Clang Sanitizers | ✓ | |
Cppcheck | ✓ | |
Facebook Infer | ✓ | |
Coccinelle | ✓ | |
Smatch | ✓ | |
Kernel-Doc | ✓ | |
Sparse | ✓ | |
cpplint | ✓ | |
GNU GCC Static Analyzer | ✓ | |
C# | Roslynator.DotNet.Cli | ✓ |
Java | FindBugs | ✗ |
SpotBugs | ✓ | |
Facebook Infer | ✓ | |
Python | Pylint | ✓ |
Pyflakes | ✓ | |
mypy | ✗ | |
Bandit | ✗ | |
JavaScript | ESLint | ✓ |
JSHint | ✗ | |
JSLint | ✗ | |
TypeScript | TSLint | ✓ |
Go | Golint | ✓ |
Staticcheck | ✗ | |
go-critic | ✗ | |
Markdown | Markdownlint | ✓ |
Sphinx | ✓ |
Clang Sanitizers
Name | Support storage of analyzer results |
---|---|
AddressSanitizer | ✓ |
ThreadSanitizer | ✓ |
MemorySanitizer | ✓ |
UndefinedBehaviorSanitizer | ✓ |
DataFlowSanitizer | ✗ |
LeakSanitizer | ✓ |
We support to convert multiple sanitizer output to a CodeChecker report directory which can be stored to a CodeChecker server by using our report-converter tool. For more information how to use this tool see the user guide.