Exact Matches

Code Insight 6.14.2 SP1

There are two types of archives: those with exact matches and those without exact matches.

Archives with Exact Matches

During a Code Insight scan, archives that are found to contain an Exact match (digest match) on the outer file are tagged with the “Contains Exact File Matches” tag, while inner files of these archives are not tagged for Exact matches and therefore will not display the tag. This behavior is in place as a performance enhancement and is reflected in the group/tag file counts. These files are still analyzed and tagged for all other evidence types, including Copyrights, Emails and/or URLs, Search Term matches and License matches. The “Contains Indicators” tag is applied to inner files of archives with Exact matches only if one of these four evidence types is detected and is not applied otherwise.

For example, if a scan reveals that foo.jar has an Exact match to a component in the Code Insight CL, it will be tagged with the “Contains Exact File Matches” tag. Its inner files however, such as foo.jar/License.txt, will not display this tag but may display other tags such as the “Contains License Matches” and “Contains Indicators.”

Archives without Exact Matches

Archives that do not contain an Exact match (digest match) on the outer file are further analyzed for Exact matches on the inner files. If an inner file is found to contain an Exact match, it will be tagged with the “Contains Exact File Matches” tag and the “Contains Indicators” tag.

For example, if a scan reveals that foo.jar does not have an Exact match to a component in the Code Insight CL, its inner files will be further analyzed for Exact matches. If foo.jar/License.txt is then identified as an Exact match to a component in the Code Insight CL, it will be tagged with the “Contains Exact File Matches” tag and the “Contains Indicators” tag, as well as any other tags reflecting the detected evidence.