[Schema Inaccuracy] Code Scanning Alert

Open

#4,728 opened on Apr 10, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 55/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: github, openapi
Domain: api, documentation

Research direction

Start with the organization code scanning alerts endpoint schema linked in the issue and inspect how its response classification enum is defined. Confirm that "documentation" is a valid observed value, then update the schema so the enum includes it and verify the endpoint description remains consistent.

Written by the indexing model from the issue text.

Description

documentation

Schema Inaccuracy

The Response Schema for the code scanning alert endpoint(for organizations) defines 4 valid values for classifications. When using this endpoint we sometimes get the value "documentation" which is not listed.

"code-scanning-alert-classification": {
        "type": "string",
        "description": "A classification of the file. For example to identify it as generated.",
        "nullable": true,
        "enum": [
          "source",
          "generated",
          "test",
          "library"
        ]
      },

Expected

The schema should include all values

"code-scanning-alert-classification": {
        "type": "string",
        "description": "A classification of the file. For example to identify it as generated.",
        "nullable": true,
        "enum": [
          "source",
          "generated",
          "test",
          "library",
          "documentation"
        ]
      },

Reproduction Steps

Due to the sensitive nature of the alerts I cannot provide an explicit example.

Dominant language: No language data
Stars: 1.6k
Forks: 342
Avg merge: 3h 33m
Merged PRs (30d): 51

Contributor guide

Open the contributing guide

First steps

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

Similar issues

[Bug]: Discord Activity titles with emoji are rejected as over 80 characters when they are not Open

clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

openclaw/openclaw#156094 · 1 comment · 1 reaction · Opened Sep 23, 2026
[Bug] Trino/Presto queries fail when query metadata contains non-ASCII characters Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

growthbook/growthbook#7100 · Opened Sep 23, 2026
Reflected XSS in loopback OAuth callback via error_description Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

punkpeye/mcp-remote#369 · Opened Sep 23, 2026
WebPubSubServiceClient.GetClientAccessUri (sync) drops the groups argument on the TokenCredential path Open

Client customer-reported needs-team-attention question Service Attention WebPubSub

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction · Opened Sep 22, 2026
`GoogleModel` returns Gemini's interim thought images as output when not streaming Open

bug p:3-mid pydanty:bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

pydantic/pydantic-ai#8643 · 1 comment · Opened Sep 22, 2026

More Backend & API Design issues