List view
Decomposition, settings, state-backend decoupling, and cyberscript groundwork for the future aces-sdl swap.
No due date•0/15 issues closedNative CTF scheduler, scoring, and participant-access work before relying on native CTF at an event.
No due date•0/5 issues closedControl-plane security and identifier hygiene required before further OSS-public exposure.
No due date•0/5 issues closedTerminal/Guacamole/networking correctness and portal performance for the next event.
No due date•0/13 issues closedThe test/validation layers that prove the pipeline and runtime, so changes are caught before an event window.
No due date•0/12 issues closedMake the dev deploy pipeline trustworthy. Gating set before any next deploy attempt of the newer path.
No due date•7/9 issues closedInternal quality work: god-module splits, cyclomatic-complexity reduction, type-checking re-enablement, and structural cleanups with no user-facing behavior change.
No due date•8/44 issues closedNice-to-haves after launch: frontend/design-system redesign, cost dashboards, notification/email surfaces, and assorted UX polish.
No due date•2/95 issues closedRange and scenario capabilities: CyberScript scenario authoring, scenario catalog, NGFW access, capacity/provisioning signaling, egress allowlists, and range lifecycle.
No due date•2/108 issues closedBring the CTF platform to general availability: event/team/participant lifecycle, scoring, challenges, notifications, import/export, and the CTF correctness/bug backlog.
No due date•1/74 issues closedMake Shifter deployable beyond the current AWS setup: GCP support, root-configured backend bundles, per-deployment configuration, and cloud-agnostic data model.
No due date•1/21 issues closedMust-fix before the public OSS release: CI/CD deploy bugs, dev→main reliability gates, security hardening, accessibility defects, repo hygiene, and dependency posture.
No due date•3/71 issues closed