Hi all, we wanted to give you advance notice of a change coming to SCA data in the detailedreport.do API output for applications that have an SCA Agent project linked to the application.

For each library in the API output in the library field, we currently report a name calculated by our SCA Upload process that is different from the name that is visible in SCA Agent output. For greater consistency and ease in matching detailedreport.do API output to SCA Agent API output and results, we will change the value in the library field to reflect the library name in the SCA Agent data.

For customers and integrations that use SCA vulnerability data via detailedreport.do, this will result in changes to the output. Depending on the nature of the integration, this may result in various outcomes. For instance, customers using the Veracode Jira integration who have mapped the library name to a Jira ticket field will see that value updated.

We expect this change to go live by June 25, 2021. Please review any integrations that use this data and contact support with any questions.