a static analysis plug-in can use this object to analyze a source file.

this object transfer to a static analysis plug-in with full information.

a static analysis plug-in should fill(not create) the fields of this object as a result of analysis.

this object will be used by the dexter-execute project(EndOfAnalysisHandler).

a Defect object indicate one defect.

a defect object can have more than one Occurence object(s) as a List

a static analysis plug-in should create a Defect or Defects List

a Occurence has a exact position information of a Defect.

a static analysis plug-in should create a Occurence or Occurence List

sometimes, it is hard to create a Defect and a Occurence objects separately.

in this case, you can create PreOccurence object, then create a Defect and a Occurence objects
from the PreOccurence object.

the dexter-execute project use a concreate class of this interface

to create an AnalysisConfig and an AnalysisResult objects.

You don't need to use this interface if you are concerns only a static analysis plug-in

• can stop system
• occurs in run-time

Memory Leak

Array Index

• a unit module can not work, but system works fine
• does not occur in run-time

• Defect but you don't need to fix immediately

• Not Defect
• for clean code

use explicit keyword

Nested If Statements

• high false alarm (over 50%)
• it can be a defect or not depends on a context

null dereference

opensource license check