Resolved Issues
The following issues were resolved in the Code Insight 2025 R2 release:
Issue |
Description |
SCA-57239 |
Scanning a requirements.txt file failed to generate inventory items with appropriate versions. This issue has been resolved. |
SCA-57214 |
A failure was observed while updating the Project report. Instead of reflecting the correct count of unique copyright entries, the Project report displayed duplicate entries. This issue has been resolved. |
SCA-56790 |
Scanning a requirements.txt file failed to detect the certifi version This issue has been resolved. |
SCA-56281 |
Inconsistencies were observed in the resulting inventory items when a .NET SDK project was scanned twice with only minor changes to package references. This issue has been resolved. |
SCA-51677 |
A user was able to create tasks for an inventory item that was generated from a different project scan, even though the same user was not permissible to edit and create tasks for the same inventory item. This issue has been resolved. |
SCA-51080 SCA-50964 |
Scanning the NPM codebase, including the v1 version of a package-lock.json file, failed to generate the dependency inventory items. This issue has been resolved. |
SCA-46385 |
Scanning a .csproj file with multiple dependency references resulted in generating an inventory item only for the last dependency referenced. This issue has been resolved. |
SCA-56648 |
A discrepancy was observed between the Get Project Inventory API response and Code Insight user interface. The API response included all possible licenses for an inventory item, even when a valid component version (CV) was already selected. In contrast, the user interface displayed only license(s) associated with the selected valid component version. This issue has been resolved. |