apsdehal / apsdehal/awesome-ctf
Proposal: New section "Workflow & Orchestration" + add MilkyWay
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
## Proposal
I would like to propose adding a new section to the `awesome-ctf` list:
**`Workflow & Orchestration`**
This section would host tools that integrate multiple CTF domains (web, crypto, forensics, reverse, binary, etc.) into a unified workflow – platforms that help competitors manage challenges, track attempts, and automate repetitive tasks, rather than focusing on a single technical area.
## Why this section is needed
Currently, the list is organised by technical domain (e.g. `Web`, `Crypto`, `Forensics`, `Reversing`). This works well for specialised tools (e.g. a new steganography finder). However, there is no natural home for **comprehensive CTF orchestrators** that:
- Provide a single shell/interface for 50+ tools across all domains
- Include built‑in version control (logging, diff, replay)
- Manage challenge workspaces (folders, notes, outputs)
- Offer AI‑powered assistance or workflow automation
These tools solve a different problem – *process management* – and deserve a dedicated, discoverable place in the list.
## Tool to add in this section
I would like to add my project **MilkyWay**:
> [MilkyWay](https://github.com/kazim-45/milkyway) – Galactic CTF orchestrator with 11 planets (web, crypto, forensics, reverse, binary, cloud, mobile, recon, passwords, AI, version control), Saturn command versioning, and Pluto AI assistant.
It fits the proposed section perfectly because:
- It unifies **11 domains** under one interactive shell (`mw>`)
- Every command is automatically logged, diffable, and replayable (Saturn)
- It scaffolds challenge workspaces with notes, outputs, and `solve.py` templates
- It includes pure‑Python fallbacks for 60+ commands – no “tool not found” errors
- It has an AI assistant (Pluto) for tool suggestions and cheatsheets
## Suggested placement
If the new section is accepted, I suggest placing it after the introductory **`Create`** section (or before `Forensics`), with the following entry:
```markdown
## Workflow & Orchestration
*Tools that integrate multiple CTF domains and manage the entire competition workflow.*
- [MilkyWay](https://github.com/kazim-45/milkyway) - Galactic CTF orchestrator with 11 planets, Saturn version control, and an AI assistant (Pluto).
If you prefer not to add a new section, I understand. In that case, the closest existing fit would be Reversing (under JavaScript Deobfuscators or at the end of that section), as MilkyWay includes a full reverse‑engineering planet (Mars) with disassemble, info, symbols, trace, and r2 integration.
Thank you for maintaining this essential resource, it has helped countless CTF players. I look forward to your feedback.
Contributor guide
Research direction
Review the current awesome-ctf list structure and the proposed MilkyWay project at https://github.com/kazim-45/milkyway. Decide whether a Workflow & Orchestration section belongs after Create or before Forensics, and whether the project fits; done means the section and entry are accepted and added, or the existing Reversing placement is chosen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100