Hi there!
I’ve just moved some linter integration plugins to the KDE infrastructure (scratch repos), therefore making them generally available.
They are fairly simple plugins, all 3 of them are alike in that they just run an external tool, and bring the results (the issues found) into KDevelop’s GUI. The found issues then will be in the problems toolview, in their own separate tab. The tools can check either a single file or all files in the project. You can see the workflow and configuration options in the videos included. There are also user’s manuals and tech manuals in the docs directories of each repo.
kdev-clangcheck
This plugin integrates Clang’s static code analysis feature, providing C/C++ static code analysis.
Git repository:
git://anongit.kde.org/scratch/laszlok/kdev-clangcheck.git
kdev-pylint
This plugin integrates a linter called Pylint, and as the name suggests it’s a Python code analyzer.
Git repository:
git://anongit.kde.org/scratch/laszlok/kdev-pylint.git
kdev-jshint
This plugin integrates a linter called JSHint, and as the name suggests it’s a Javascript code analyzer.
Git repository:
git://anongit.kde.org/scratch/laszlok/kdev-jshint.git
dfighter1985 
Unfortunately, JSHint is not Free Software. It is derived from JSLint and therefore inherits its non-Free license. We really need a JS linter plugin using one of the linters not derived from JSLint.
Hi there Kevin!
First of all, thanks for the feedback!
Yes you are right! Others have also told me this, and also that major distributions wouldn’t include this plugin because of this, even if the plugin itself doesn’t contain any non-free code, just depend on a non-free package.
Anyhow I’ll see what I can do!
[…] New linter integration plugins for KDevelop […]