FlexNet Code Insight 2019 R3
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 final “notices” text associated with the inventory item. It is pulled from the Notices Text field on the License & Notices tab for a selected inventory item in Analysis Workbench or in Project Inventory. If this field is empty, FlexNet Code Insight uses the content in the As-Found License Text field (also on the License & Notices tab), which shows the verbatim text license text found in the codebase by the system. If no As-Found License Text or Notices Text information is available, the text pulled from the FlexNet Code Insight data library for the selected license is used in the Notices report. For more information, see Finalizing the Notices Text for the Notices Report |
FlexNet Code Insight 2019 R3 Help LibraryOctober 2019 |
Copyright Information | Flexera |