- This line was added.
- This line was removed.
- Formatting was changed.
This section will guide you through the functions of the Kiuwan Insights module.
|Table of Contents|
Kiuwan Insights Dashboard:
Introduction to Kiuwan Insights
Today’s time-to-market imposes high pressure on releasing new versions of your application. Productivity becomes essential. And most of the time, you will Many applications incorporate external open source and third-party components that let you enable developers to build new functionality very fast and with minimum effort.
Open Source repositories provide huge amounts of software that lets you build new applications very fast and robustly.
But not all are benefits; there might be also some drawbacks when using open source components.quickly and efficiently. But while the use of open source components has many benefits, it also introduces risk. Kiuwan Insights helps you manage this risk by providing answers to the key questions described below.
Kiuwan Insights comes to answer all these questions by providing:
Kiuwan Insight analyzes your application software, discovering all external dependencies, and builds a components inventory that lets you track any external piece of code that could be part of your application.
Go to Insights > Components to access the components inventory.
Supported languages and resources
Kiuwan Insights uses the following resources to extract information on 3rd party dependencies.
From these sources, Kiuwan Insight builds the Components Inventory of your application.
You can add your specific private (local or remote) and/or public repositories by properly configuring Kiuwan Local Analyzer.
Please visit Insights - Additional Maven repositories for further information.
Security, Obsolescence, and Licensing
At a glance, Kiuwan Insights provides detailed information and visual indicators that quickly let you know the different levels of risk associated with every external component.
Every component is assigned a level (High, Medium, Low or None) on three different risk metrics:
- Security Risk (due to vulnerabilities introduced by components)
- Obsolescence Risk (due to using obsolete components)
- License Risk (due to legal implications of used components’ licenses)