Red team: November 2026

Offen
  • Stimmt etwas nicht?
#1,494 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
5/100
Issue-Typ
Dokumentation
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Bereich
security

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
TypeScript
Sterne
5
Forks
1
Ø Merge
10 Std. 54 Min.
Gemergte PRs (30 T.)
438

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus diffplug/dormouse

Alle Issues in diffplug/dormouse

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.