FlexNet Code Insight 2019 R1
FlexNet Code Insight provides the ability to produce a Notices report to satisfy the attribution requirements of most open source licenses. The report is created in text format.
After Engineering has completed the remediation plan, resolving all rejected inventory items, the codebase is rescanned until it is approved for release. When the codebase is approved for release, you need to generate a Notices report to accompany the software application. This report is a compilation of all the open source/third-party components contained in the product and their license content (notices).
The Notices report shows only published inventory. The inventory can be system-generated or custom and of any type—Work in Progress, Component, or License.
The following items can appear in the Notices report for each inventory item:
| • | Inventory name—The entry in this field is based on naming conventions, which is usually the component name, version, and governing license name. |
| • | Inventory URL—If the inventory URL is not available, FlexNet Code Insight uses the associated component URL. If both are unavailable, no URL will appear in the report. |
| • | Inventory Notices Text— The “notices” text associated with the inventory item. It is pulled from the Notices Text pane on the Inventory Details panel in the Analysis Workbench (or on the Notes & Guidances tab on the Project Inventory page). If this pane is empty, FlexNet Code Insight uses the content in the As-Found License Text pane, which shows the verbatim text license text found in the codebase either by the system or the Analyst. If no As-Found License Text or Notices Text information is available, no notices are generated for the inventory item in the Notices report (although the report will still show the inventory name and the URL, if available). |
FlexNet Code Insight 2019 R1 Help LibraryMarch 2019 |
Copyright Information | Flexera |