Skip to content

Compliance: codeql-default-setup-not-configured #92

Closed

Description

@don-petry

Compliance Finding

Category: ci-workflows
Severity: error
Check: codeql-default-setup-not-configured

Detail

CodeQL default setup is in state {"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"} (expected configured). Run apply-repo-settings.sh markets or gh api -X PATCH repos/petry-projects/markets/code-scanning/default-setup -F state=configured -F query_suite=default.

Standard Reference

standards/ci-standards.md#2-codeql-analysis-github-managed-default-setup

Remediation

Please review the linked standard and bring this repository into compliance.

See the full standards documentation for implementation guidance.


This issue was automatically created by the weekly compliance audit.

Activity

  1. don-petry commented on Apr 9, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-04-09)

    This finding is still open.

    Detail: CodeQL default setup is in state {"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"} (expected configured). Run apply-repo-settings.sh markets or gh api -X PATCH repos/petry-projects/markets/code-scanning/default-setup -F state=configured -F query_suite=default.

    Standard: standards/ci-standards.md#2-codeql-analysis-github-managed-default-setup

  2. don-petry commented on Apr 9, 2026

    @don-petry
    ContributorAuthor

    Claude encountered an error —— View job


    I'll analyze this and get back to you.

  3. don-petry commented on Apr 10, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-04-10)

    This finding is still open.

    Detail: CodeQL default setup is in state {"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"} (expected configured). Run apply-repo-settings.sh markets or gh api -X PATCH repos/petry-projects/markets/code-scanning/default-setup -F state=configured -F query_suite=default.

    Standard: standards/ci-standards.md#2-codeql-analysis-github-managed-default-setup

  4. don-petry commented on Apr 14, 2026

    @don-petry
    ContributorAuthor

    Claude finished @don-petry's task in 3m 18s —— View job • claude/issue-92-20260414-1257 • Create PR ➔


    CodeQL Default Setup — Compliance Fix

    • Gather context (repo stack, existing workflows, org standards)
    • Determine correct approach: GitHub-managed default setup (not a workflow file)
    • Enable GitHub-managed CodeQL default setup via API (state=configured, query_suite=default, run_id: 24189956214)
    • Delete drift .github/workflows/codeql.yml (standard: workflow file and default setup are mutually exclusive)
    • Commit & push
    • Open PR — petry-projects/markets#105
    • CI green (all checks passed)
    • Tagged @don-petry for review

    What was done

    The compliance audit was flagging codeql-default-setup-not-configured. Per org standard ci-standards.md §2, CodeQL must use GitHub-managed default setup — not a per-repo workflow file. The two are mutually exclusive and leaving both causes double CI billing.

    1. Enabled GitHub-managed default setup via gh api -X PATCH (state=configured, query_suite=default)
    2. Deleted .github/workflows/codeql.yml (marked as drift by the standard)
  5. added a commit that references this issue on Apr 14, 2026
    02d8b9e
  6. don-petry commented on Apr 17, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-04-17)

    This finding is still open.

    Detail: CodeQL default setup is in state {"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"} (expected configured). Run apply-repo-settings.sh markets or gh api -X PATCH repos/petry-projects/markets/code-scanning/default-setup -F state=configured -F query_suite=default.

    Standard: standards/ci-standards.md#2-codeql-analysis-github-managed-default-setup

  7. don-petry commented on Apr 18, 2026

    @don-petry
    ContributorAuthor

    Claude finished @don-petry's task in 3m 7s —— View job • claude/issue-92-20260418-1841 • [Create PR ➔](https://github.com/petry-projects/markets/compare/main...claude/issue-92-20260418-1841?quick_pull=1&title=Issue%20%2392%3A%20Changes%20from%20Claude&body=This%20PR%20addresses%20issue%20%2392%0A%0AGenerated%20with%20%5BClaude%20Code%5D(https%3A%2F%2Fclaude.ai%2Fcode)


    CodeQL Default Setup — Compliance Fix

    What was done

    The GitHub-managed CodeQL default setup was already configured on this repo. The only remaining drift was .github/workflows/codeql.yml — PR #105 from the previous attempt was never merged, so the file persisted. Per ci-standards.md §2, having both the workflow file and default setup simultaneously causes double CI billing and is treated as drift by the compliance audit.

    Why the compliance audit still shows 403: The audit's PAT lacks the security_events: read permission needed to call /code-scanning/default-setup, so it gets HTTP 403 and treats that as "not configured". This is an org-level infra issue — the audit token in .github org secrets needs security_events: read (fine-grained PAT) or repo scope (classic PAT) to read code scanning state. Merging this PR completes the repo-side fix; the token permissions fix needs to happen in the org's .github secrets.
    • Branch: claude/issue-92-20260418-1841

  8. added a commit that references this issue on Apr 18, 2026
    0c72d7d
  9. 5 remaining items

  10. don-petry commented on May 1, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-01)

    This finding is still open.

    Detail: CodeQL default setup is in state {"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"} (expected configured). Run apply-repo-settings.sh markets or gh api -X PATCH repos/petry-projects/markets/code-scanning/default-setup -F state=configured -F query_suite=default.

    Standard: standards/ci-standards.md#2-codeql-analysis-github-managed-default-setup

  11. don-petry commented on May 8, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-08)

    This finding is still open.

    Detail: CodeQL default setup is in state {"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"} (expected configured). Run apply-repo-settings.sh markets or gh api -X PATCH repos/petry-projects/markets/code-scanning/default-setup -F state=configured -F query_suite=default.

    Standard: standards/ci-standards.md#2-codeql-analysis-github-managed-default-setup

  12. don-petry commented on May 11, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-11)

    This finding is still open.

    Detail: CodeQL default setup is in state {"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"} (expected configured). Run apply-repo-settings.sh markets or gh api -X PATCH repos/petry-projects/markets/code-scanning/default-setup -F state=configured -F query_suite=default.

    Standard: standards/ci-standards.md#2-codeql-analysis-github-managed-default-setup

  13. don-petry commented on May 12, 2026

    @don-petry
    ContributorAuthor

    Weekly Compliance Audit (2026-05-12)

    This finding is still open.

    Detail: CodeQL default setup is in state {"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"}{"message":"Resource not accessible by personal access token","documentation_url":"https://docs.github.com/rest/code-scanning/code-scanning#get-a-code-scanning-default-setup-configuration","status":"403"} (expected configured). Run apply-repo-settings.sh markets or gh api -X PATCH repos/petry-projects/markets/code-scanning/default-setup -F state=configured -F query_suite=default.

    Standard: standards/ci-standards.md#2-codeql-analysis-github-managed-default-setup

  14. don-petry commented on May 12, 2026

    @don-petry
    ContributorAuthor

    Resolved! This check is now passing as of 2026-05-12. Closing automatically.

  15. added 3 commits that reference this issue on May 13, 2026
    daa9083
    a4d2591
    96f3579
  16. added
    dev-leadFor dev-lead agent pickup
    and removed
    dev-leadFor dev-lead agent pickup
    on Jun 2, 2026
  17. don-petry commented on Jun 5, 2026

    @don-petry
    ContributorAuthor

    Resolved! This check is now passing as of 2026-06-05. Closing automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    compliance-auditAutomated compliance audit findingdev-leadFor dev-lead agent pickup

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions