OStatic

By Sunar Mahad on Jun. 11, 2007

Take a look at Zend Studio. It is not free but it has some code analysis features like flagging possible errors (unused variables, single use variables for possible typos and others)

By Marco Foley on Jun. 12, 2007

For real basic tests first, you can just run php -l . This will point out some basic compile time errors. There are a few other tools like RATS and SWAAT that mainly check for security vulnerabilities.

By Marco Foley on Jun. 12, 2007

I had a similar task, btw, and spent some time looking at the tools mentioned above, along with some free trials of commercial tools like Fortify. Ended up doing what you were thinking of - writing a quick analyzer for specific insight of queries used across the files. Dumped the results into a db so I could check on progress as we changed urls across the site from dynamic to static.

By Brad Wilson on Jun. 25, 2007

You can also spend some time using xdebug, and view the output in kcachegrind. Both of these are open source. xdebug had some issues with the zend optimizer, so you might need to turn that off when you use it. Another word of caution - xdebug log files might be left on, and depending on how aggressively you are logging, those logs could grow very fast! A good way to do this - set up your code, and run it a few times - run a smoke test or something. Then analyze the output. Following that, you can add your custom statements and analyze flow that way. Once you know the major files and methods being called, you can dig deeper. Hope this was of use.

By Zviki Cohen on Oct. 15, 2009

Check out nWire: a new Eclipse plugin for PHP code exploration. nWire analyzes your code and extracts all the components and associations. It then provides an interactive visual components of your code structure.

There's much more, check it out: http://www.nwiresoftware.com/products/nwire-php