"A BIG BALL OF MUD is haphazardly structured, sprawling, sloppy, duct-tape and bailing wire, spaghetti code jungle. We’ve all seen them. These systems show unmistakable signs of unregulated growth, and repeated, expedient repair. Information is shared promiscuously among distant elements of the system, often to the point where nearly all the important information becomes global or duplicated. The overall structure of the system may never have been well defined. If it was, it may have eroded beyond recognition. Programmers with a shred of architectural sensibility shun these quagmires. Only those who are unconcerned about architecture, and, perhaps, are comfortable with the inertia of the day-to-day chore of patching the holes in these failing dikes, are content to work on such systems." [Big Ball of Mud]

There are moments in time when you need to check the internal structure of a program to verify. The easiest method to do it is to check the dependencies between elements of code. And with a dependency graph generated you can see if your program did not started to look like spaghetti.

Information for users

Here you can find information for users - how to download and use the project.


Not yet available.


Not yet available.

Information for developers

Here you can find information interesting for developers which would like to get the sources, provide improvements or create their own version.


Project repository:

Build instruction

This project uses Maven. You can import the project into Eclipse with m2e plugin.


Depchecker is released under MPL 2.0 license.