...
- Previously, in the responses, the alert UUID was the same for all vulnerabilities related to the same library name. After enabling this feature, the alert UUID is unique per CVE and therefore different for all the vulnerabilities related to the same library.
- A new element has been added (sourceFiles) to the API response in case there is a relation between a CVE and a source file.
- The following fields were added to the responses of the APIs: getAlerts, getAlertsByProjectTag, getProjectAlertByType in all the scopes (project/product/organization):
- Modified Date
- Alert Status
- Comment
Removed APIs
Additionally, the following is a list of APIs that are not available to organizations if Vulnerability-based Alerting is installed:
- getOrganizationAlertsReport
- getProductAlertsReport
- getProjectAlertsReport
- getOrganizationIgnoredAlertsReport
- getProductIgnoredAlertsReport
- getProjectIgnoredAlertsReport
- getOrganizationResolvedAlertsReport
- getProductResolvedAlertsReport
- getProjectResolvedAlertsReport
| Info |
|---|
Changes in the APIs do not cause any backward compatibility issues. |
Unaffected APIs
For the remaining APIs that have not been affected by the transition to Vulnerability-based Alerting, see the following:
NOTE: In case there is a relation between a CVE and a source file, the following elements will be added to the API response:
| Code Block |
|---|
//This is the new element that was added to the response in case the alerts relate to a source file
"sourceFiles": [
{
"name": "swagger-ui.min.js",
"sha1": "0d1935e6d5d00a2c096989f5de2e08d8b2446d96",
"systemPath": "dist/swagger-ui.min.js",
"lastModified": "2019-08-28",
"bytes": 0,
"numOfLines": 0,
"id": 6574351
}
]
|