|
1167
|
1 |
.. -*- coding: utf-8; -*-
|
|
|
2 |
|
|
|
3 |
================
|
|
|
4 |
Code analysis.
|
|
|
5 |
================
|
|
|
6 |
.. contemts::
|
|
|
7 |
|
|
|
8 |
About.
|
|
|
9 |
======
|
|
|
10 |
|
|
|
11 |
* http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis
|
|
|
12 |
|
|
1170
|
13 |
Splint.
|
|
|
14 |
=======
|
|
|
15 |
|
|
|
16 |
Secure Programming Lint, is a programming tool for statically checking C
|
|
|
17 |
programs for security vulnerabilities and coding mistakes. Formerly called
|
|
|
18 |
LCLint, it is a modern version of the Unix lint tool.
|
|
|
19 |
|
|
|
20 |
http://en.wikipedia.org/wiki/Splint_%28programming_tool%29
|
|
|
21 |
|
|
|
22 |
Sparse.
|
|
|
23 |
=======
|
|
|
24 |
|
|
|
25 |
Sparse is a tool designed to find possible coding faults in the Linux kernel.
|
|
|
26 |
|
|
|
27 |
http://en.wikipedia.org/wiki/Sparse
|
|
|
28 |
Wikipedia page.
|
|
|
29 |
|
|
1167
|
30 |
PMD.
|
|
|
31 |
====
|
|
|
32 |
|
|
|
33 |
PMD is a static ruleset based Java source code analyzer that identifies
|
|
|
34 |
potential problems.
|
|
|
35 |
|
|
|
36 |
PMD has plugins for JDeveloper, Eclipse, JEdit, JBuilder, Omnicore's CodeGuide,
|
|
|
37 |
NetBeans/Sun Studio, IntelliJ IDEA, TextPad, Maven, Ant, Gel, JCreator, Hudson,
|
|
|
38 |
Jenkins, Sonar and Emacs.
|
|
|
39 |
|
|
|
40 |
http://pmd.sf.net/
|
|
|
41 |
Home page.
|
|
|
42 |
http://en.wikipedia.org/wiki/PMD_%28software%29
|
|
1168
|
43 |
Wikipedia page.
|
|
|
44 |
|
|
1171
|
45 |
Checkstyle.
|
|
|
46 |
===========
|
|
|
47 |
|
|
|
48 |
Static code analysis tool used in software development for checking if Java
|
|
|
49 |
source code complies with coding rules.
|
|
|
50 |
|
|
|
51 |
http://en.wikipedia.org/wiki/Checkstyle
|
|
|
52 |
Wikipedia page.
|
|
|
53 |
|
|
|
54 |
FindBugs.
|
|
|
55 |
=========
|
|
|
56 |
|
|
|
57 |
http://en.wikipedia.org/wiki/FindBugs
|
|
|
58 |
Wikipedia page.
|
|
|
59 |
|
|
1174
|
60 |
Pychecker.
|
|
|
61 |
==========
|
|
|
62 |
|
|
|
63 |
http://en.wikipedia.org/wiki/Pychecker
|
|
|
64 |
Wikipedia page.
|
|
|
65 |
|
|
|
66 |
Pylint.
|
|
|
67 |
=======
|
|
|
68 |
|
|
|
69 |
http://en.wikipedia.org/wiki/Pylint
|
|
|
70 |
Wikipedia page.
|
|
|
71 |
|
|
1173
|
72 |
JSLint.
|
|
|
73 |
=======
|
|
|
74 |
|
|
|
75 |
JSLint is a static code analysis tool used in software development for checking
|
|
|
76 |
if JavaScript source code complies with coding rules.
|
|
|
77 |
|
|
|
78 |
It is provided primarily as an online tool, but there are also command-line
|
|
|
79 |
adaptations.
|
|
|
80 |
|
|
|
81 |
http://en.wikipedia.org/wiki/JSLint
|
|
|
82 |
Wikipedia page.
|
|
|
83 |
|
|
1172
|
84 |
Squale.
|
|
|
85 |
=======
|
|
|
86 |
|
|
|
87 |
Squale (Software Quality Enhancement) is an open-source platform that helps
|
|
|
88 |
monitoring software quality for multi-language applications. It currently
|
|
|
89 |
supports Java out-of-the-box, and can also analyse C/C++ and Cobol code with an
|
|
|
90 |
adapter to McCabe tool. Squale is distributed under the terms of the LGPL v3
|
|
|
91 |
licence.
|
|
|
92 |
|
|
|
93 |
http://en.wikipedia.org/wiki/Squale
|
|
|
94 |
Wikipedia page.
|
|
|
95 |
|
|
1168
|
96 |
Yasca.
|
|
|
97 |
======
|
|
|
98 |
|
|
|
99 |
Yasca leverages external open source programs, such as FindBugs, PMD, JLint,
|
|
|
100 |
JavaScript Lint, PHPLint, Cppcheck, ClamAV, Pixy, and RATS to scan specific file
|
|
|
101 |
types, and also contains many custom scanners developed for Yasca.
|
|
|
102 |
|
|
|
103 |
http://yasca.org/
|
|
|
104 |
Home page.
|
|
|
105 |
http://yasca.org/
|
|
|
106 |
Development home page.
|
|
|
107 |
http://en.wikipedia.org/wiki/Yasca
|
|
|
108 |
Wikipedia page.
|
|
|
109 |
|
|
1169
|
110 |
Sonar.
|
|
|
111 |
======
|
|
|
112 |
|
|
|
113 |
Sonar uses various static code analysis tools such as Checkstyle, PMD, FindBugs,
|
|
|
114 |
Clover to extract software metrics.
|
|
|
115 |
|
|
|
116 |
http://en.wikipedia.org/wiki/Sonar_%28software_quality%29
|
|
1172
|
117 |
Wikipedia page.
|
|
|
118 |
|