Extend CodeQL to the actions language and settle the query suite
Los mantenedores suelen responder en 4 días
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 70/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, yaml
- Área
- developer-experience, devops, security
Línea de trabajo
Start with .github/workflows/codeql.yml, add the issue's actions analysis configuration, and run the workflow against .github/workflows/. Record the default-suite and security-extended alert counts, triage the actions findings, and document the code-scanning dismissal policy in TRIAGE.md. Done means actions analysis runs, the query-suite decision and comparison numbers are recorded, and the dismissal policy states who may dismiss alerts and which reason codes are allowed.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem statement
Follow-up to #298 and the workflow merged in #335.
#298 asked for SAST covering "the website (JS/TS) and workflow/config surfaces". The workflow that landed in #335 covers the first half only: a matrix entry for javascript-typescript, which extracts 274 files from website/** and scripts/ and reports 0 findings against 87 rules.
The workflow half was assumed to need a different tool. It does not: CodeQL ships an actions language with its own extractor and security queries (github/codeql/actions/ql/src/Security), covering CWE-094 (code injection in workflows), CWE-829 (unpinned or third-party actions), CWE-312 (cleartext credentials), plus CWE-275, CWE-285 and CWE-349.
Nothing in this repo analyses .github/workflows/, which is the highest-privilege code here: deploy.yml holds pages: write and id-token: write.
Separately, the query suite was never chosen, only defaulted. The baseline is 87 rules and 0 results, which is a clean starting point but says nothing about what security-extended would surface.
Proposed solution
- Add
- language: actionswithbuild-mode: noneto the matrix in.github/workflows/codeql.yml, run it, and confirm whether this repo's workflows analyse cleanly without extra configuration. - Run
security-extendedon a throwaway branch and compare the alert count with the default suite. Decide, and record the numbers in this issue. - Add the dismissal policy to
TRIAGE.md: who may dismiss a code scanning alert, and which reason codes are acceptable.
If the actions queries turn out to be thin, the fallback is actionlint in CI for syntax and shellcheck, and zizmor for workflow security rules. Do not add a second scanner before testing the one already being installed.
Scope and impact
One matrix line plus a comparison run. The risk is noise: if security-extended or the actions queries produce a wall of findings, the gate gets ignored, so the baseline has to be triaged before either change lands as a default.
Acceptance criteria:
-
actionsanalysis runs and its findings are triaged - Query suite chosen, with the comparison numbers recorded here
-
TRIAGE.mdstates the dismissal policy for code scanning alerts
- Lenguaje dominante
- TypeScript
- Estrellas
- 13
- Forks
- 24
- Merge medio
- 2 d 3 h
- PR fusionados (30 d)
- 16
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de IntersectMBO/developer-experience
-
Rename the q4-2025 sesion-notes folder to session-notes, and keep its URL workingPosiblemente ocupada @IanoNjuguna la tomó hoy. Abiertodocumentation Low Priority
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
IntersectMBO/developer-experience#406 ·
Los mantenedores suelen responder en 4 días
-
react 19: the Dependabot halves cannot resolve alone, so the bump needs one combined PRPosiblemente ocupada @IanoNjuguna la tomó hoy. Abiertodependencies
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
IntersectMBO/developer-experience#403 ·
Los mantenedores suelen responder en 4 días
-
Document colour roles in the brand baseline, and resolve the gradient and alpha restrictions it contradictsPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertodocumentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
IntersectMBO/developer-experience#376 ·
Los mantenedores suelen responder en 4 días
-
documentation pinned
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
IntersectMBO/developer-experience#363 · 1 comentario ·
Los mantenedores suelen responder en 4 días
-
documentation pinned
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
IntersectMBO/developer-experience#362 · 1 comentario ·
Los mantenedores suelen responder en 4 días
Todos los issues de IntersectMBO/developer-experience
Issues similares
-
[UI] Guard webApis against undefined window in SSR environmentsPosiblemente ocupada @madhavzanwar la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
headroomlabs-ai/headroom#4992 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
paperclipai/paperclip#22575 ·
Los mantenedores suelen responder en 1 día
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
lingdojo/kana-dojo#34502 · 1 comentario · 5 reacciones ·
Los mantenedores suelen responder en 1 día
-
bug frontend good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
nikhilb2/simple_invoicing#935 ·