Skip to content

Enhancement | Decide which repos get CodeQL and secret scanning (after removing Snyk) #2

Open

Description

@diego-ojeda-binbash

What?

Review the org's repos and decide where to turn on CodeQL (code scanning) and secret scanning with push protection.

Why?

This came up while removing Snyk from leverage (binbashar/leverage#358, binbashar/leverage#380):

  • The org's Snyk is on the free plan. Its quota ran out on the first day of each billing period. A re-import brought in 5237 projects from every repo, and all of them were deleted on 2026-11-15.
  • The free plan also had no API access and no full vulnerability database (fullVulnDB: false).
  • In leverage, Snyk was replaced by Dependabot (dependencies), CodeQL default setup (python + actions) and secret scanning with push protection. On public repos these are free and have no quota.

Scope

  • Public repos (190): CodeQL and secret scanning are free. Candidates are repos with code or workflows that are actively maintained.
  • Private repos (40): both need GitHub Advanced Security, which is paid. Decide whether it's worth it, or leave them out.

Proposal

  1. List the active public repos (recent pushes, not archived) and the languages CodeQL supports.
  2. Turn on secret scanning + push protection on all public repos. It has no CI cost.
  3. Turn on CodeQL default setup on the active repos with code or GitHub Actions workflows.
  4. Check whether Dependabot alerts and security updates are already on in the same repos.
  5. Optionally set these as org defaults for new repos (Settings → Code security → Configurations).

🤖 Generated with Claude Code

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions