This page offers an overview of which technologies are supported by Kiuwan.
Since Feb 2020 = GO
Since Dec 2019 = Kotlin
Kiuwan supports 30+ different technologies and this set is continuously growing as we develop new parsers.
Below you can find the current set of supported technologies.
If you do not find a specific technology, or you have any questions, do not hesitate to contact us (Contact Kiuwan Technical Support)
Kiuwan provides built-in engines to process different technologies.
Below you can find the default mapping between technologies and file extensions.
When Kiuwan processes source files, it will apply the engine based on the found file extension.
For more information regarding those languages, please contact the Kiuwan support team.
The above mapping is the default used by Kiuwan, but it can be fully customized in several ways.
Full customization can be done using Kiuwan Local Analyzer
The most common need for custom configuration is when your source files belong to a supported technology but with a different extension.
In this case, you can add that extension to Kiuwan.
For example, if you Cobol files have “ .cobol” extension, you could add “cobol” to COBOL’s extension list.
In this way, when Kiuwan finds source files with “ .cobol” extension, it will trigger the COBOL technology parser and apply COBOL rules.
Customization can be done in two ways:
Here are further instructions:
To apply an extension-technology mapping to all analyses (even of other applications), follow the instructions below.
This mechanism allows you to modify the extensions associated with the technologies, keeping the current set of applicable technologies.
To apply an extension-technology mapping to all analyses of a specific application, follow the instructions below:
There are some special cases where the same extension (for example .sql) matches more than one technology (in this case, PL-SQL, Transact-SQL and Informix).
If you analyze your code in the Cloud or with Kiuwan Local Analyzer Graphical User Interface (GUI), you will be asked to select the technology to apply to that analysis. In that way, Kiuwan will apply the selected technology to those files in that analysis.
But, if you run the analysis through Kiuwan Local Analyzer Command-Line Interface (CLI), by default the analysis will apply all the matching engines to those files, resulting in a waste of time and resources as well as producing confusing results (the whole set of rules for every technology will be run against the same sources).
In CLI mode, we strongly suggest you to properly configure Kiuwan to avoid this situation and only apply the right Kiuwan engines.
Depending on the needs, there different solutions.