Build Your Own OSINT Platform: 10 GitHub Projects You Can Chain

Extend the existing real username-search app with optional public-profile enrichment. Read the current soxoj/maigret and soxoj/socid-extractor documentation first. Choose a supported integration: direct socid-extractor parsing for known supported profile pages, or a bounded Maigret search with enrichment. Explain which path you chose. Don't assume Maigret is a generic URL-only enrichment API.

Add an Enrich selected profiles action. Show only fields actually extracted, such as display name, bio, avatar URL, account creation date, public statistics, account ID and explicitly published links. Keep unavailable fields empty. Store a source URL and retrieval time for every observation. Separate reported profile text from your own inferences.

Add a Cytoscape.js graph. Use distinct relationship types for same username and explicitly linked profile. Clicking a node shows its evidence. Do not merge accounts into a confirmed person just because names or avatars match. Do not generate personality, sensitive-trait or location inferences.

Keep recursive expansion off until the user requests it. Then cap depth, requests and runtime. Deduplicate requests and cache briefly. Use only approved public HTTP(S) destinations; block private, loopback, link-local and metadata addresses, including after DNS resolution and each redirect. Never fetch arbitrary file URLs. Apply these checks to remote avatars too.

Stream real enrichment events into the existing terminal UI. Keep the graph readable on mobile. Verify source attribution, blocked pages, missing fields, job ownership and cancellation. Preserve all working search features.

Build a public web-asset inventory for authorized domains using projectdiscovery/subfinder, projectdiscovery/dnsx and projectdiscovery/httpx. Inspect current upstream documentation and use supported structured outputs. Do not confuse ProjectDiscovery httpx with Python HTTPX.

Require an explicit domain allowlist and ownership verification or an administrator-approved scope before active checks. Collect passive subdomain candidates, resolve them, then perform low-rate HTTP checks only on in-scope public destinations. Block private, loopback, link-local and cloud metadata destinations. Validate DNS answers and redirects. Stop rather than follow an out-of-scope redirect.

Show hostname, discovery source, DNS answers, observed status, page title, technology hints and last-checked timestamp when available. Preserve unknown and blocked states. Do not label a host vulnerable based on its title or technology fingerprint. No exploitation, brute force, port scans or login attempts.

Use a dark terminal dashboard with animated real events, searchable inventory, per-host details, CSV export and cancellation. Store provider keys only in server secrets. Report which passive sources are configured and which are unavailable. Add a queue, request budgets and per-domain concurrency limits. Verify the workflow using a domain I control; ask for that domain if none is provided.

Add a Check my file module using the official ExifTool project. Accept explicitly uploaded user-owned photos and supported documents. Run a pinned ExifTool version in an isolated backend worker with strict file-size, type, execution-time and output limits. Do not execute uploaded content or accept remote URL fetching.

Display only metadata returned by the tool. Group fields into device information, timestamps, document authorship and location tags when present. Explain that missing GPS does not mean a processing failure and that metadata can be edited.

Never publish uploads. Isolate user access, delete temporary files after processing, and provide Clear results. No fabricated example metadata in the actual result screen. Match the existing terminal styling and verify malformed files, unsupported formats, oversized uploads and deletion.