- Revenera Community
- :
- Code Insight
- :
- Code Insight Forum
- :
- Re: Inconsistencies between "As-Found License Text" file path and "Associated Files"
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Inconsistencies between "As-Found License Text" file path and "Associated Files"
Hello Flexera team,
In 2019.R2 I'm finding random inconsistencies between the As-Found License Text file path vs. Associated Files.
e.g. abbrev 1.0.9 (ISC)
Associated Files: /tw-src/LATEST/ip360-vne-latest/artifacts/npm/abbrev/1.0.9/abbrev-1.0.9.tgz
As-Found License Text: The following text is found in file:LICENSE at /tw-src/LATEST/ip360-vne-latest/artifacts/yum/centos-6/com/nodesource/rpm/nodejs/6.6.0-1nodesource.el6.centos.x86_64/nodejs-6.6.0-1nodesource.el6.centos.x86_64.rpm
The license text is correct for abbrev 1.0.9, but the file paths do not match.
so far I found this to be true for
abbrev 1.0.9 (ISC)
commander 2.9.0 (MIT)
The following text is found in file:LICENSE at /tw-src/LATEST/ip360-vne-latest/artifacts/npm/bower/1.8.0/bower-1.8.0.tgz
Associated files: /tw-src/LATEST/ip360-vne-latest/artifacts/npm/commander/2.9.0/commander-2.9.0.tgz
concat-map 0.0.1 (MIT)
The following text is found in file:LICENSE at /tw-src/LATEST/ip360-vne-latest/artifacts/yum/centos-6/com/nodesource/rpm/nodejs/6.6.0-1nodesource.el6.centos.x86_64/nodejs-6.6.0-1nodesource.el6.centos.x86_64.rpm
Associated files: /tw-src/LATEST/ip360-vne-latest/artifacts/npm/concat-map/0.0.1/concat-map-0.0.1.tgz
LP,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @lpopescu,
We sincerely apologize for our lack of response. Going forward, we will be making a concerted effort to respond to all forum questions in a timely manner as well as responding to all previously asked questions on our forum. If you or someone else still has this question, here is our response:
In the first example you gave, there are two separate detections taking place. The first is for the component, abbrev 1.0.9 (ISC), which came from the associated file mentioned. The second is a license file detection which is used to populate the As-Found License Text. These two detections are then mapped to the same inventory due to the ISC license associated to that particular component version in our data library.
In a case where no license text is detected, default license content from the Code insight data library will be used instead.