Bugs related to unscoped variables can sometimes be extremely difficult to find and reproduce, especially with a large code base. Unfortunately, I've had to learn this the hard way. I decided that it would be a good idea to take a proactive approach to this rather than a reactive approach, and that's how this project was born.

You may have already seen Seth Petry-Johnson's varScopeChecker, another great tool that has the same goal as varScoper. Unfortunately I didn't discover his tool until I was 90% of the way through my 1.0 version. This meant it didn't really make sense to combine the two. I was able to find some cases that he handled that I didn't and I've tried to incorporate as many of these as possible. The best approach would probably be to run both of these tools to analyze your code.

I also want to thank my employer, Planitax, for generously allowing me to contribute this code to the community.


Huge Thanks to Pat Santora for providing invaluable enhancements to the cfscript parsing mechanism, and numerous bug fixes/enhancements.

Thanks to Zac Spitzer for writing the code to identify var statements within cfscript.

Thanks to Harry Klein for helping to resolve issues related to cfscript that were reported on RIAForge.

Kola Oyedegi - addition of XML output.

Dmitriy Goltseker - fix for directory processing in CF 6/7/8

Please take a look at the roadmap if you are interested in helping out.