There was an incorrect component detection for GitForWindows and Tidebugger components as shown below:
Details
GitForWindows => you should refine the scope by excluding some typical folders prior to running the scan (e.g. .git folders) as recommended in the article below.
https://doc.casthighlight.com/good-practices-defining-scope-code-scan/
Environment-specific files and folders
For more consistent results, SCM, build and deployment folders (e.g. .git, .svn, gradle, .circleci, .scannerwork, .azure, .vscode, etc.) or files (e.g. .yaml, .gitignore, .gitmodules, Makefile, .npmignore, .checkstyle, build.xml, gradlew… this list is not exhaustive) shouldn’t be part of the scope. For a more complete list of files and folders you should typically exclude from the scan scope, refer to this Github repository that lists these exclusions by technology stack.
Jquery => this is a known limitation of the product (old versions of Jquery are not published in the forges that we crawl, hence this fingerprint is mapped with the component having the oldest occurrence in the SCA database).
Additional Resources
CAST Highlight Troubleshooting Guides
CAST Highlight Product Documentation
Zendesk Ticket Number
#29054
Comments