If you get warnings either at the overview page or at the editor page, somethings is wrong within the analysed component. The overview page will show warnings, if the textdomain can not be found clearly. In this case the author has written the components code in a way make it hard to detect.
Warnings at the editors view will show up, if the component is using badly coded textdomains. This could be either by integration of other plugins code or accidentally by typing mistakes.
Reported issues are not a problem of Codestyling Localization, it’s caused by the author of the affected component within it’s code.
Ah. Yes, this has been reported before. I disagree with what the plugin is saying here, and I’m not going to make changes just for it. However, other upcoming changes in WordPress in the next month or two might result in me making a change which in turn should stop the localisation plugin reporting rubbish warnings.