This FAQ provides quick answers to common questions about Code Insight, including installation, configuration, troubleshooting, and best practices.

1. Is there a different process for installing customer reports on newer versions of Code Insight?

Answer

No. The installation process for custom reports remains the same across all versions. Follow the steps documented in the GitHub repository to install all reports using the report installer:

https://github.com/flexera-public/sca-codeinsight-reports-installer

Or, refer to the link below to install specific reports as per your needs:

https://github.com/orgs/flexera-public/repositories?language=&q=sca&sort=&type=all

2. Can newer versions of reports be installed on older versions of Code Insight?

Answer

Check the prerequisite section of each report to confirm version compatibility. For newer versions of Code Insight (2024 or later), reports are generally version-independent and can be installed on any version of Code Insight. However, this may change as new reports are released, so it’s best to refer to the official documentation for the latest guidance.

3. Does insufficient disk space affect product functionality? Can the UI still be accessed?

Answer

Adequate disk space is required for Code Insight to function properly. Operations such as Electronic Update, Library Refresh, and inventory updates will fail if disk space is insufficient. Exhausted disk space may also result in HTTP 404 or 403 errors when accessing the web UI. Ensure sufficient free space before performing operations.

4. Why are users unable to log in after migrating to version 2025 R4?

Answer

The password handling mechanism has changed in FNCI 2025 R4. Reset user and admin passwords using the following credentials:

• User: CodeInsight_2025R4 
• Password: Password123

Refer to the Code Insight Installation & Configuration Guide for details.

5. Does Code Insight use Python 3.x?

Answer

Code Insight does not use Python out of the box. However, Python 3.x is required during the installation of custom reports and when generating them.

6. Can inventory analysis and modifications be performed during an electronic update?

Answer

No. Operations such as auditing, publishing, and inventory changes rely on database transactions. Performing these actions during an electronic update can cause:

• Database locks
• Update failures
• Data integrity issues

Avoid concurrent operations during updates.

7. Why is project creation or codebase upload failing or taking too long?

Answer

There can be multiple reasons for this issue such as:

• Scanner service not active: The scanner must be running and properly configured before creating new projects or uploading codebases. If it’s inactive or misconfigured, uploads will fail.
• High queue volume: When multiple projects are being uploaded simultaneously, the queue can become congested, causing delays.
• Large codebase size: Uploading very large codebases or projects with numerous files can significantly increase processing time.
• Network latency or bandwidth issues: Slow or unstable network connections can impact upload speed and cause timeouts. In such case the project upload will fail silently without any error logging.
• Insufficient code base path privileges: If the user running the Code insight lacks with the privileges on the code base path, then project upload might fail.

8. Why does the component lookup feature fail for some GitHub repositories? Does source matching depend on star count?

Answer

Component lookup does not work for repositories with fewer than 50 stars. This limitation ensures relevance and quality. Source-code matching is unaffected; scans will still create inventories for detected components.

9. How are exact matches different from source matches? How are exact matches detected?

Answer

• Source Match: Source Match typically relies on line-by-line fuzzy matching. It begins by extracting the first 64 bits of content from the file and comparing them against entries in the Compliance Library (CL). It then shifts one bit to the right and repeats the comparison, continuing this process iteratively.
• Exact Match: Occurs when file content fully matches an entry in the Compliance Library. Such files appear under the Exact Matches tab.

A minimum number of consecutive matching lines is required for detection.

10. Why can some users not be disabled in the Administration page?

Answer

Only users created through the Users/Permissions page present in Administration menu can be disabled. LDAP-synced users cannot be disabled from the Users/Permissions web UI.

11. How can inventory creation with zero associated files be avoided?

Answer

Enabling the option On data import or re-scan, delete inventory with no associated files in Project Summary Page > Edit Project > General will prevent inventory creation with zero associated files.

NOTE: Manually created/modified inventories won't be affected by the above explained option. Manual intervention can be checked via View History option present in Inventory Details in Analysis Workbench or in Project Inventory page.