Selecting Materials to Scan

FlexNet Code Insight 2019 R3

In preparing a project for scanning, you must identify which materials to scan and configure the project to point to these materials. The way in which you do this will largely depend on the type of scan you are performing:

Traditional scan where the codebase is uploaded to the Scan Server or synchronized using a source code management system (SCM) such as Git or Perforce. With a traditional scan, you can manually move the code to the Scan Server, upload the code, or configure the project with an SCM. See these locations for instructions:
Uploading a Project Codebase
Configuring Source Code Management chapter
Remote scan using a FlexNet Code Insight scan agent plugin to perform a scan remotely within the context of an Engineering application (such as an IDE, source-management, artifact-repository, CI, build, testing, or installation application). With a remote scan, the FlexNet Code Insight scan agent plugin is configured to scan remotely and send results to FlexNet Code Insight for review and remediation. See the following for more information:
Creating a Project Without Uploading a Codebase in the “Performing Inventory-Only Scanning” chapter
FlexNet Code Insight Plugins Guide (available for download in the Flexera Customer Community)

In both traditional and remote scan scenarios, the results are processed by FlexNet Code Insight, which creates inventory, detects licenses and security vulnerabilities, applies policies for automated review, and creates review and remediation tasks per configuration.