CSVLint is useful in terms of identifying potential parsing issues, though I think the larger issue is that very few applications actually generate valid CSV files - even Excel has it's issues with certain encodings.
In most cases programmers seem to have an incorrect set of assumptions around encodings, escaping etc.
I'm a software tester, but the company I work for gets a lot of third-party data from CSV files, which frequently do not match the requirements set out for those files. Using a CSV validation tool (ideally a web service controlled by the company I work for) would allow our clients to validate the files before they sent them to us.
I'm slowly putting together my own solution for this, but if suitable open-source software already exists I'd be happy to make use of or modify that.
In most cases programmers seem to have an incorrect set of assumptions around encodings, escaping etc.