Open Source Source Code Analysis Tools

Doxygen is a JavaDoc like documentation system for C++, C, Java and IDL.

qpt (Qt Project Tool) understands Qt C++ projects (.pro) and allows to pass this information to command line tools as "Code Counters" and "Static Analysis tools". It also can used inside QtCreator to act as a plugin for "Static Analysis tools" putting reported issues into QtCreator issues pane.

cline is a command line tool that counts code lines or non-whitespace characters in your project folder. It is designed to recursively find any source file matching specific rules and count the line breaks within that file. You may specify file suffixes to include or exclude as well as regular expressions for code lines that shall be excluded (e.g. to exclude comments). By default a heuristic algorithm skips binary files. You may configure the restrictiveness of this algorithm with command line options.

CoFlo generates Control-Flow Graphs from C and C++ source code. It can then output the graphs in a number of ways and perform various control flow analyses. NOTE: CoFlo has not been under active development for several years. At this time, I suggest you look into LLVM-based tooling to see if there is anything similar to CoFlo which will meet your needs.

DEEEP is a open source static analysis tool to detect, in C programs, integer vulnerabilities caused by the bad adaption of aplications from ILP32 to LP64. It uses the tools Lint and Splint, and runs over Open Solaris and Linux operating systems. This tool semantically analyses source code. More precisely, it does type checking, data-flow analysis, and it automatically correlates the results of these two types of analysis. Type checking is used for finding bugs on the way integers are handled, and data-flow analysis is used to see if hazardous functions (eg. memcpy, strcpy) are accessible from outside the program. After this two analyses, the tool correlates the results from the previous phases to attain if the data that comes from the inputs are affected by vulnerabilities from porting to LP64, and if these are handled by dangerous functions (memcpy, strcpy,...). In resume, identify if the found bugs

Often I have seen some Huge Maintenance Projects it is always very difficult to track the incremental files for each release and If we want to do that we need to checkout both the branches and use some UI based tool to get the diff of the files finally we end up waiting in front of the PC for a long time and do this job. In many cases we spend more than 2 hrs/day. The time increases if there are more such parallel releases and at the end of the day 1 developer does it as full time job and has zero productivity. I thought of adding value here. This just gets the diff files. Can be used for Static code analysis like PMD to do PMD only for the delta. The current status of the project is in Development". If you wish to add something please mail me.

This is a python program which generates python file for a given .glade file (LibGlade fmt)

This package will allow people to check, change, update the license of their projects. It will conform to all new licenses available.

Counts the Lines of Code for any type of source file (Java, C/C++), given the single line comment and muli line comment (configurable)

XRay is an analysis tool built upon your SCMs, aimed to consolidade project statistics from many repositories in a single tool, generating code reports and development statistics obtained from log data and file versions.

A command-line Python utility to mine information on open source projects using the ohloh web service APIs. The script is enables analysis of open source projects indexed by ohloh by providing source lines of code (SLOC), contributor data and other info.

The 'pysourceinfo' package provides source information on Python runtime objects based on 'inspect', 'sys', 'os', and 'imp'. The covered objects include packages, modules, functions, methods, scripts, and classes by two views: - File System View - packages, modules, and linenumbers - based on files and paths - Runtime Object View - callables, classes, and containers - based on in-memory RTTI / introspection The supported platforms are: - Linux, BSD, Unix, OS-X, Cygwin, and Windows - Python2, Python3 - CPython, PyPy Object addresses within modules - Object Identifier OID - and the display of the runtime call flow are supported by 'PyStackInfo'. Online documents: https://pysourceinfo.sourceforge.io/