Upcoming changes to GitHub Dependabot alerts REST API offset-based pagination parameters (`page`, `first`, and `last`)
We’re closing down offset-based pagination parameters (page
, first
, and last
) in all GitHub Dependabot alerts REST API endpoints. Going forward, only cursor-based pagination parameters (before
, after
, and per_page
) will be supported. This change brings GitHub Dependabot alerts in line with other GitHub security APIs, and simplifies how you retrieve large sets of alerts.
What’s changing
You’ll no longer be able to use page
, first
, or last
parameters when listing Dependabot alerts via the REST API. This affects the following endpoints:
- List Dependabot alerts for a repository
- List Dependabot alerts for an organization
- List Dependabot alerts for an enterprise
To paginate through results, use these cursor-based parameters instead:
before
after
per_page
Why we’re making this change
Cursor-based pagination is more consistent, reliable, and performant than offset-based pagination. By standardizing on cursor-based pagination, we’re making it easier for you to work with large datasets and align your integrations across GitHub security APIs.
Timeline and next steps
- Offset-based pagination parameters (
page
,first
, andlast
) will be removed from all Dependabot alert endpoints on October 14, 2025. - Please update your scripts and integrations to use cursor-based parameters as soon as possible
For more details on how cursor-based pagination works in the API, see the GitHub API documentation. For more information on the working with Dependabot, see the Dependabot Alerts API documentation.
Join the discussion within GitHub Community.