Trend of historical alerts (Beta)

Trend analytics of historical alerts.

This endpoint consumes 10 units of your quota.

This endpoint requires the following org token scopes:

  • historical:alerts-trend
Log in to see full request history
Path Params
string
required

The slug of the organization

Query Params
string
Defaults to CURRENT_DATE

The UTC date in YYYY-MMM-DD format for which to fetch alerts

string
Defaults to -7d

The number of days of data to fetch as an offset from input date

string

Comma-separated list of fields that should be used for count aggregation (allowed: alertSeverity,repoSlug,alertType,artifactType,alertAction,alertCategory)

string
Defaults to monitor,warn,error

Comma-separated list of alert actions ("error", "warn", "monitor", or "ignore) that should be included

string

Comma-separated list of alert categories ("supplyChainRisk", "maintenance", "quality", "license", or "vulnerability") that should be included

string

Comma-separated list of alert severities ("low", "medium", "high", or "critical") that should be included

string

Comma-separated list of alert types (e.g. "usesEval", "unmaintained", etc.) that should be included

string

Comma-separated list of artifact types (e.g. "npm", "pypi", "gem", "maven", "golang", etc.) that should be included

string

Comma-separated list of repo slugs that should be included

Responses

Language
Credentials
Click Try It! to start a request and see the response here! Or choose an example:
application/json