Klever

Implemented in juliet-suit.

To make this working use source code and Makefiles without any modifications. Then build with Clade the build base using target "individuals". You can disable collecting data with CIF or keep at least callgraph to speedup the process. Then copy the base and modify both meta.json files here setting two different options sets:

"Info.extra_CIF_opts":["-DINCLUDEMAIN", "-DOMITBAD"]

"Info.extra_CIF_opts":["-DINCLUDEMAIN", "-DOMITGOOD"]

After that you can run the Klever framework providing it with these two build bases for good and bad test cases.
Note! That it will take really a lot of time, maybe a day or even more, since there are more that 50k tests in this job. Use for that a virtual machine, VerifierCloud cluster or anything else with maximum parallelism. After the run you will see a table with matching and wrong verdicts as that one which Klever provides for tests.

And an extra minor note. To run a single test or several tests use regular expressions or object file names like "testcases/CWE122_Heap_Based_Buffer_Overflow/s08/CWE122_Heap_Based_Buffer_Overflow__c_CWE805_char_snprintf_64.out" in the job json file. Also you can run "juliet:empty" and "juliet:memory safety" rules.

Now it does not seem that the Juilet test suite is good for benchmarking Klever. So, let's consider it later.

Anyway, the branch should be rebased according to the latest master.