How alpkeskin/mosint works
Project type and purpose
• Project Type: A Go-based command-line OSINT (Open Source Intelligence) tool
• Purpose: Given an email address, it orchestrates calls to multiple external services (breach databases, social APIs, DNS lookup, Google Search, etc.), verifies and consolidates the results, and outputs them (JSON or console) for security researchers.
File structure
Top-level artifacts:
• Dockerfile, example-config.yaml, static/ (logo/images), README, LICENSE
Versioned Go module at v3/:
– cmd/mosint/main.go → CLI entrypoint
– internal/ → core orchestration modules
· config/ (config loader, API-key management)
· runner/ (coordinates tasks)
· spinner/ (console progress indicator)
· output/ (JSON or console formatting)
– pkg/ → pluggable task implementations
· dns (DNS/IP lookups)
· engine (core execution engine)
· scrape/googlesearch
· services/* (Breachdirectory, HaveIBeenPwned, psbdmp, etc.)
· social/* (Twitter, Instagram, Spotify)
· verification (email verification)
Key README insights
• Describes supported features (breach lookup, social media, paste dumps)
• Notes use of a YAML config file for API keys
• Emphasizes lightweight, fast CLI operation
• Mentions Docker support
Detail
• Parallel branches from Runner to each Task Module
• YAML config file as an external dependency loaded at startup
• Docker build/runtime contexts if relevant (e.g., container interfaces)