Summary
EvalOps does not use CodeQL. The org security baseline is enforced with Code Security / CodeQL disabled, but GitHub still reports active managed workflow tombstones at dynamic/github-code-scanning/codeql on three repos.
Live evidence from 2026-05-21
Org security configuration:
- Config
245233: EvalOps security baseline recommended
enforcement: enforced
advanced_security: secret_protection
code_scanning_default_setup: disabled
Affected active repos:
| Repo |
Workflow ID |
Path |
State |
Repo Code Security |
evalops/platform |
267390102 |
dynamic/github-code-scanning/codeql |
active |
disabled |
evalops/cerebro |
264147529 |
dynamic/github-code-scanning/codeql |
active |
disabled |
evalops/chat |
254727389 |
dynamic/github-code-scanning/codeql |
active |
disabled |
Verification already done:
gh search code 'codeql org:evalops path:.github/workflows' returns [].
gh search code 'github/codeql-action org:evalops' returns no checked-in workflow usage.
- Open org CodeQL alerts:
0.
- Branch protection/rulesets have no CodeQL / Code Quality / code scanning required checks.
- Latest dynamic CodeQL runs are older than the current enforced disable state:
platform: 2026-05-03T03:33:57Z
cerebro: 2026-05-21T00:42:02Z
chat: 2026-05-21T00:42:03Z
Attempts already made:
- Re-attached config
245233 directly to platform, cerebro, and chat; API returned {}.
GET /repos/<repo>/code-scanning/default-setup now returns 403 Code Security must be enabled for this repository to use code scanning, confirming code scanning is functionally off.
PUT /repos/<repo>/actions/workflows/<id>/disable still returns 422 Unable to disable this workflow, because these are GitHub-managed dynamic workflows.
Acceptance criteria
GET /repos/<repo>/actions/workflows/<id> for the three workflow IDs above no longer returns state: active, or the workflows disappear from /actions/workflows entirely.
- No new
dynamic/github-code-scanning/codeql runs are created after 2026-05-21T04:42:55Z.
- Org config
245233 remains enforced with code_scanning_default_setup: disabled.
- Checked-in workflows remain free of
github/codeql-action and *codeql* workflow paths.
Notes
This is a GitHub-managed workflow tombstone, not a checked-in workflow problem. The user-side disable API is blocked, so this should stay open until GitHub Support/backend GC clears the managed workflow state.
Summary
EvalOps does not use CodeQL. The org security baseline is enforced with Code Security / CodeQL disabled, but GitHub still reports active managed workflow tombstones at
dynamic/github-code-scanning/codeqlon three repos.Live evidence from 2026-05-21
Org security configuration:
245233:EvalOps security baseline recommendedenforcement: enforcedadvanced_security: secret_protectioncode_scanning_default_setup: disabledAffected active repos:
evalops/platform267390102dynamic/github-code-scanning/codeqlactivedisabledevalops/cerebro264147529dynamic/github-code-scanning/codeqlactivedisabledevalops/chat254727389dynamic/github-code-scanning/codeqlactivedisabledVerification already done:
gh search code 'codeql org:evalops path:.github/workflows'returns[].gh search code 'github/codeql-action org:evalops'returns no checked-in workflow usage.0.platform:2026-05-03T03:33:57Zcerebro:2026-05-21T00:42:02Zchat:2026-05-21T00:42:03ZAttempts already made:
245233directly toplatform,cerebro, andchat; API returned{}.GET /repos/<repo>/code-scanning/default-setupnow returns403 Code Security must be enabled for this repository to use code scanning, confirming code scanning is functionally off.PUT /repos/<repo>/actions/workflows/<id>/disablestill returns422 Unable to disable this workflow, because these are GitHub-managed dynamic workflows.Acceptance criteria
GET /repos/<repo>/actions/workflows/<id>for the three workflow IDs above no longer returnsstate: active, or the workflows disappear from/actions/workflowsentirely.dynamic/github-code-scanning/codeqlruns are created after2026-05-21T04:42:55Z.245233remains enforced withcode_scanning_default_setup: disabled.github/codeql-actionand*codeql*workflow paths.Notes
This is a GitHub-managed workflow tombstone, not a checked-in workflow problem. The user-side disable API is blocked, so this should stay open until GitHub Support/backend GC clears the managed workflow state.