How fastfire/deepdarkcti works
Project type and purpose
• deepdarkCTI is not a traditional multi-tier application but a content-centric, static documentation site.
• It collects and organizes Cyber Threat Intelligence (CTI) sources from Deep/Dark Web channels as Markdown files and publishes them as a browsable website.
• Contributors propose new sources (via Telegram, Twitter) and update the repository; end users (CTI analysts) consume the published site.
File structure
• Top-level items: LICENSE, README.md, and a set of category files (counterfeit_goods.md, telegram_infostealer.md, ransomware_gang.md, etc.).
• No “src” or “backend” code—content only.
• Implied use of a static site generator (Jekyll, Hugo) and GitHub Pages (or similar) for hosting.
• No explicit build scripts present, but standard GitOps CI/CD (e.g., GitHub Actions) is a best practice here.
README for insights
• Describes project goal, categories of sources, contribution workflow, external community channels (Telegram group), and donation integration.
Main components
a. Content Source Layer
• GitHub Repository (Markdown files grouped by CTI category)
• Contributors (via pull requests)
b. Build/Deployment Layer
• CI/CD Pipeline (GitHub Actions or equivalent)
• Static Site Generator (Jekyll/Hugo)
c. Hosting & Delivery Layer
• Hosting Platform (GitHub Pages / Netlify / Vercel)
• CDN (optional layer for performance)
d. Integration & Community Layer
• Telegram Group API (source proposals, discussion)
• Twitter Account (announcements, access requests)
• BuyMeACoffee (donation widget)
e. Consumers
• CTI Analysts / General Users browsing the published site
Relationships & Data Flows
• Contributors push updates → GitHub Repo
• GitHub Repo change triggers → CI/CD Pipeline
• Pipeline runs Static Site Generator → produces static HTML/CSS/JS
• Pipeline deploys → Hosting Platform (GitHub Pages)
• End Users → browse the site via web
• Users / Contributors → interact via Telegram & Twitter
• Users → donate via BuyMeACoffee widget embedded on site
Architectural patterns & design principles
• Content-as-Code: treat Markdown files as versioned source
• GitOps: repository-driven deployment
• Static Site Generation: simple, low-ops, highly cacheable
• Separation of concerns: content, build, deploy, consume
• GitHub (Repo + Actions)
• Jekyll or Hugo (static site generator)
• GitHub Pages / Netlify / Vercel (hosting/CDN)
• Telegram API, Twitter API
• BuyMeACoffee embed