Red team: November 2026

Abierto
  • ¿Algo no está bien?
#1,494 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
5/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Activo
Área
security

Línea de trabajo

This is a maintainer tracking issue for a monthly red-team pass, not a code change. The process is defined in docs/specs/security-audit.md under "Red team"; read that section first. Done means every checklist item is ticked, confirmed findings are fixed or documented, and the summary sections below are filled in. Only maintainers with access to the private ledger can do this work.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

red-team

The monthly red-team pass (docs/specs/security-audit.md → "Red team"): an open-ended review of the code and the published guarantees, without the FAIL IF lines, on at least two model families. Findings go to the private ledger first; this issue records the pass once its findings are fixed or documented and disclosed.

Checklist
  • Build one stripped tree per engine from main, and record the commit reviewed.
  • Run each engine: Claude through Anthropic's Cyber Verification Program, Codex through OpenAI's Daybreak program (optionally Gemini).
  • Run each engine's second round, which proves its claims against the real code.
  • Verify every claimed break with a separate reviewer.
  • File each confirmed item in the ledger, fix it in a plain-worded PR, and close it citing the PR.
  • Record the pass in the private red-team/runs/.
  • After the nightly audit discloses the fixed findings, summarize the pass here and close.
The most serious findings

Nothing found allowed an account takeover or remote access to a terminal. Confirm or replace this sentence, and say why it holds. Everything rated above low is described below. Which release fixes it, and which releases were affected.

Severity What could happen Who could do it Fixed in
Severity What could happen, in one bolded sentence. How, in plain words. Who could do it. PR

Low-severity findings, fixed or documented: each in a clause with its PR, or none.

This month
  • Passes: each pass's commit and engines.
  • Fixed: PRs.
  • Documented as not defended or a known gap: PRs.
  • Disclosed: security-audit-finding.
  • Process changes it led to: PRs, or none.
Lenguaje dominante
TypeScript
Estrellas
5
Forks
1
Merge medio
11 h 41 min
PR fusionados (30 d)
432

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de diffplug/dormouse

Todos los issues de diffplug/dormouse

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.