How faisalulde/security-writeups works
This repository is a content-only security portfolio, not a software application. Its architecture is centered on Markdown documentation organized into a small set of topic collections, with the root README acting as the landing page.
1. Top-level role
- The root README.md is the primary index and public-facing overview.
- It introduces the author, summarizes capabilities, and links into the writeup collections below.
2. Primary content boundaries
- The repo is split into two main collections:
- boroCTF-2026/ for boroCTF challenge writeups
- 0xV01D-CTF-2026/ for 0xV01D CTF writeups
- Each collection is a self-contained set of Markdown case studies.
3. Writeup unit of architecture
- Each challenge file is one independent document describing a single target, exploit path, and lessons learned.
- Examples:
- boroGPT.md
- Kobenis-Dashboard.md
- My-Mayor-Muslim.md
- Silent-Oracle.md
- Action-Packed.md
- The-Altered-Grimoire.md
4. Navigation and information hierarchy
- The root README provides the highest-level navigation, including challenge tables, categories, difficulty, and techniques.
- This gives the repo a catalog → collection → article structure:
- portfolio overview
- CTF event grouping
- individual exploit writeups
5. Supporting assets
- boroCTF-2026/screenshots/ is a media support folder for evidence images.
- These screenshots are not core logic; they support the narrative in the Markdown writeups by showing payloads, responses, or exploitation results.
6. Meta/index file
- SUMMARY.md likely serves as a table of contents for a documentation renderer or book-style navigation.
- Architecturally, it acts as an alternate index layer over the same Markdown content.
7. Data flow through the repo
- The flow is editorial, not runtime:
- author documents a challenge in Markdown
- screenshots are referenced as supporting evidence
- README and summary files link readers into the relevant writeups
- There is no backend, database, build pipeline, or executable code path.
8. Content themes and specialization
- The writeups are grouped around offensive web security techniques such as SQLi, JWT confusion, SSTI, LFI, access control flaws, and race conditions.
- This gives the repository a technical taxonomy that mirrors the way an engineer might diagram the author’s skill coverage.
9. Operational context
- The repository represents a personal security portfolio and CTF research archive.
- The external services referenced in the README, such as LinkedIn and GitHub, are profile links only; they do not affect the repository’s internal structure.
10. What to diagram
- If drawing architecture, depict:
- a root documentation hub
- two event-based documentation branches
- per-challenge Markdown nodes under each branch
- a screenshots asset store feeding selected writeups
- a summary/navigation layer that points into the same content
- Do not model any runtime services, APIs, or data processing components, because none are present.
Overall, this repo is best understood as a static knowledge repository with a simple hierarchical document structure and a separate asset folder for supporting evidence.
Main entry points: boroCTF-2026 boroCTF 2026 · 0xV01D-CTF-2026 0xV01D 2026 · screenshots Screenshots · README.md README
Components 11
Documentation Hub
Root index and alternate table-of-contents layer for the portfolio.
boroCTF 2026
Writeups from the boroCTF 2026 event.
- boroCTF 2026 · Collection of challenge writeups for the boroCTF 2026 event.
boroCTF-2026 - boroGPT · Single challenge case study and exploit narrative.
boroCTF-2026/boroGPT.md - Kobenis Dashboard · Single challenge case study and exploit narrative.
boroCTF-2026/Kobenis-Dashboard.md - My Mayor Muslim · Single challenge case study and exploit narrative.
boroCTF-2026/My-Mayor-Muslim.md
0xV01D 2026
Writeups from the 0xV01D CTF 2026 event.
- 0xV01D 2026 · Collection of challenge writeups for the 0xV01D CTF 2026 event.
0xV01D-CTF-2026 - Action Packed · Single challenge case study and exploit narrative.
0xV01D-CTF-2026/Action-Packed.md - Silent Oracle · Single challenge case study and exploit narrative.
0xV01D-CTF-2026/Silent-Oracle.md - Altered Grimoire · Single challenge case study and exploit narrative.
0xV01D-CTF-2026/The-Altered-Grimoire.md
Support Assets
Media used as evidence inside selected writeups.
- Screenshots · Supporting evidence images referenced by writeups.
boroCTF-2026/screenshots
Connections 15
- README → boroCTF 2026: links to · Primary navigation into the boroCTF writeup collection.
- README → 0xV01D 2026: links to · Primary navigation into the 0xV01D writeup collection.
- README → SUMMARY: indexes · Provides an alternate entry point for the same Markdown corpus.
- SUMMARY → boroCTF 2026: toc for · Table-of-contents layer points into the boroCTF collection.
- SUMMARY → 0xV01D 2026: toc for · Table-of-contents layer points into the 0xV01D collection.
- boroCTF 2026 → boroGPT: contains · Collection contains individual challenge writeups.
- boroCTF 2026 → Kobenis Dashboard: contains · Collection contains individual challenge writeups.
- boroCTF 2026 → My Mayor Muslim: contains · Collection contains individual challenge writeups.
- boroCTF 2026 → Screenshots: supports · Screenshot assets support selected boroCTF writeups.
- Screenshots → boroGPT: evidence for · Evidence images may be embedded or referenced by the writeup.
- Screenshots → Kobenis Dashboard: evidence for · Evidence images may be embedded or referenced by the writeup.
- Screenshots → My Mayor Muslim: evidence for · Evidence images may be embedded or referenced by the writeup.
- 0xV01D 2026 → Action Packed: contains · Collection contains individual challenge writeups.
- 0xV01D 2026 → Silent Oracle: contains · Collection contains individual challenge writeups.
- 0xV01D 2026 → Altered Grimoire: contains · Collection contains individual challenge writeups.