kibit is a static code analyzer for Clojure, ClojureScript, cljx and other Clojure variants.
Patterns to include in reports.
Note: The input patterns are not applied when running kibit in order to follow the source paths of each Leiningen project. Therefore, some of the files excluded by the patterns may be processed and you may even see logs related to the excluded files in the job console. However, Inspecode eventually ignores any issues detected on the excluded files when generating job reports.
Patterns to exclude from reports.
Note: Just like
input:, the ignore patterns are not applied when running kibit.
Specifying true implies
Amount of CPU. The default machine has
0.75 CPU with
2880 MiB RAM.
Inspecode configures the maximum heap size (
-Xmx) of the Java virtual machine (JVM) by applying a custom profile with
:jvm-opts according to this value.
240 MiB RAM for system, and makes the rest of RAM available to JVM for heap allocation.
-Xmx2640m is specified by default (for
-Xmx5520m is specified for
No tool specific severity levels are available.
Note: The incremental analysis is not supported for kibit as of now due to the same reason as
With default options:
inspecode: kibit: default
With enabling auto-fixing and default options:
inspecode: kibit: auto-fix
With custom machine:
inspecode: kibit: machine: cpu: 1.5 # 1.5 CPU, 5760 MiB RAM
If there are multiple Leiningen projects (
project.clj files) in single repository, Inspecode detects them and then runs
kibit for each project.
The dependencies are resolved in the same manner as
lein test. See the
lein test page for the details.