Open Source Java Source Code Analysis Tools

Some software measures are still not widely used in industry, despite the fact that they were defined many years ago, and some additional insights might be gained by revisiting them today with the benefit of recent lessons learned about how to analyze their design. This project analyzes the design and definitions of Halstead’s metrics, the set of which is commonly referred to as ‘software science’. This analysis is based on a measurement analysis framework defined to structure, compare, analyze and provide an understanding of the various measurement approaches presented in the software engineering measurement literature.

Runtime concurrency analysis for Java. Instruments your Java app at run time, and monitors field access, synchronization and locking, to verify concurrent access is safe.

Java library to parse GNU Makefiles. The source code is available from SVN. The latest revision should be in trunk, the latest "stable" release should be in branch.

Justus is a tool set for Progress 4GL (ABL) Developers. It includes a simplified parser for 4GL, an API to load Profiler data and a Test Coverage Tool.

NPEDetector is a tool for statically detecting the dereferences in Java programs that are safe and those that could potentially result in NullPointerException. Designed to be a sound verifier, NPEDetector guarantees the safety of proven dereferences but could imprecisely flag safe dereferences as faulty. NPEDetector is built using WALA, Watson Libraries For Analysis.

A toolbox for testing SQL. Currently, SQL Spelunk includes code coverage analysis and calling stored procedures in a rolled-back transaction from SQL and JUnit.

XJML 1.0 actually can reads one Java class and its contract (written in XML) and then executes the next verification techniques: 1. Runtime Assertion Checking (RAC). Using JML4c and JML4rt tools. 2. Extended Static Checking (ESC). Using ESC/Java2. 3. Full Static Program Verification (FSPV). Using the Why platform (tested with Why 2.30 and Why3 0.71)

gcRadar is not a static code anayser but it is a library using which is ment to beused in your source code and it will monitor and report the lifetime events of yuor objects. gcRadar can provide this information by using callbacks, log4j & polling. gcRadar can monitor entities ranging from individula objects to full object trees comprising of is-a & has-a relationships. By using gcRadar you can monitor the lifetime of the objects that are created by your application in runtime, gcRadar enables the application to be aware of the memory constaraints that arise at runtime. The workings of the mythical Java Garbage Collector have for long eluded the common developer. Now by gcRadar enable you to record the life and death of objects at runtime.

Its an Eclipse 3.5 Plugin. It can be used to find linear paths for unit testing of any method. The linear path covers all the child methods and till leaf level of the hierarchy. The packages which should be covered in the path can be controlled.

Recognizes typical patterns in Java code which could be replaced with functions provided by open source libraries http://www.jnorm.org