
That's a very interesting feedback and thanks a ton for this. The important point to recognize is that with CAST promotes a unique risk-driven assessment model, where the idea is instead of focussing to fix all the violations in particular source file, rather we should identify top riskiest transactions or components that are essentially critical for degrading a particular health measure(Robustness, Efficiency, Security....so on and so forth) and this is exactly where CAST stands out from the other source code analysis tools which essentially focusses on maintainability issues and blindly ask developers the fix all of them in a particular source file/ directory. We, at CAST, believe the best way to really improve the HEALTH of software is to be able to understand what is important and what is necessary.
More views on this topic are very much welcome.