Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Schema Inaccuracy] /orgs/{org}/dependabot/alerts schema is missing 'page'

Open Beginner friendly
#4,350 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
openapi
Domain
api

Research direction

Start by locating the OpenAPI schema for GET /orgs/{org}/dependabot/alerts and compare its parameters with the linked Dependabot documentation and other organizational alert endpoints. Add the missing page parameter and verify that the schema matches the endpoint’s pagination links and supports generated clients using page.

Written by the indexing model from the issue text.

Description

documentation

Schema Inaccuracy

The API endpoint to get dependabot alerts for an org/enterprise do not contain the page parameter.

When calling these endpoints, the returned links for rel=next etc. include the page parameter. Using the page parameter in subsequent requests works like expected, therefore the schema seems to be inconsistent with the implementation here.

https://docs.github.com/en/rest/dependabot/alerts?apiVersion=2022-11-28#list-dependabot-alerts-for-an-organization

Other Organizational Alert Endpoints (Secret Scanning etc.) have the page parameter specified in the schema.

Expected

The schema should include the page parameter for the endpoint.

Reproduction Steps

  1. Call Endpoint
  2. Response data returns links with the page set in the links section.

As I am using an lib that is auto generated from the schemas this creates issues as it tries to use a value for page on an object that does not know 'page'.

Thanks :)

Dominant language
No language data
Stars
1.6k
Forks
342
Avg merge
2h 23m
Merged PRs (30d)
57

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/rest-api-description

All issues in github/rest-api-description

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.