ALL SYSTEMS CAVE |
zero trackers · zero cookies open source · agplv3 + mit three devs · one cave hosted in the eu zero trackers · zero cookies open source · agplv3 + mit three devs · one cave hosted in the eu
zéro traceurs · zéro cookies open source · agplv3 + mit trois devs · une cave hébergé en europe zéro traceurs · zéro cookies open source · agplv3 + mit trois devs · une cave hébergé en europe
| PARIS · --:--
corploc CorpLoc
ship it
corploc / tools / gitsint
// tool · beta ·

find who's behind
the commits.
trouve qui se cache
derrière les commits.

OSINT platform for GitHub intelligence. Crawls social graphs, detects leaked secrets, correlates identities, and visualizes everything in a real-time interactive graph. Plateforme OSINT pour le renseignement GitHub. Crawl les graphes sociaux, détecte les secrets leakés, corrèle les identités, et visualise le tout dans un graphe interactif en temps réel.

~/cave · gitsint
$ curl -X POST localhost:3000/api/v1/scans/discover \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"target": "corploc", "type": "user"}'
→ scan started: scan_7f3a...
→ streaming events via SSE...

→ node_discovered: user/hokanosekai
→ node_discovered: user/glider
→ node_discovered: repo/gitsint (12 commits)
→ edge_discovered: hokanosekai → OWNS → gitsint
→ identity_found: arsene@2600.eu (confidence: 0.95)
→ leak_found: AWS key in config.yml (severity: high)
→ scan complete: 3 users, 8 repos, 2 leaks
$
stars
language
latest version
45+
secret validators
// 01

how it works

3 steps · no surprises
// 01

deploy.

docker compose up — spins up the API (Go), workers (Rust), NebulaGraph, Redis, TimescaleDB, and the React frontend.

// 02

scan.

Enter a GitHub username, org, or repo. Discover crawls the social graph. Analyze deep-scans repos for secrets and identities.

// 03

explore.

Watch the interactive graph build in real time via SSE. Inspect nodes, trace relationships, validate leaked secrets against live APIs with 45+ WASM modules.

// 02

use cases

3 scenarios

security teams

Map contributor networks across GitHub repos to identify shadow IT, leaked credentials, and exposed identities before they're exploited.

bug bounty hunters

Discover forgotten API keys and tokens buried in commit history. Validate them instantly against live APIs with built-in WASM modules.

osint investigators

Correlate git commit identities across repos. Link email addresses, PGP keys, and co-author tags to build a profile from public data.

// 03

origin story

Gitsint started as a quick Python script to extract emails from git logs. Then we needed to cross-reference identities across repos, so we added a graph database. Then we needed to validate found secrets, so we built WASM modules. Then we needed real-time visualization, so we added SSE streaming and Sigma.js. What was supposed to be a 200-line script is now a multi-service platform — but it still does the same job, just a lot better.

Gitsint a commencé comme un script Python rapide pour extraire des emails des git logs. Puis on a eu besoin de croiser les identités entre les repos, donc on a ajouté une base de données de graphes. Puis on a eu besoin de valider les secrets trouvés, donc on a construit des modules WASM. Puis on a eu besoin de visualisation en temps réel, donc on a ajouté du streaming SSE et Sigma.js. Ce qui devait être un script de 200 lignes est devenu une plateforme multi-services — mais le job reste le même, en beaucoup mieux.

// 04

comparisons

honest positioning

Maltego

Maltego is broader — email, social media, DNS, infrastructure. Gitsint goes deeper on GitHub specifically: graph visualization, secret validation, identity correlation across commits.

TruffleHog

TruffleHog scans for secrets in git repos. Gitsint does that too, but adds the social graph layer — who contributed what, where, and what identities are behind the commits.

GitDorker

GitDorker uses GitHub search dorks. Gitsint clones repos and runs deep analysis — commit-level scanning, not just search results.

// 05

threat model

All data stays on your infrastructure. No telemetry, no phone-home, no cloud dependency. Toutes les données restent sur ton infra. Pas de télémétrie, pas de phone-home, pas de dépendance cloud.

  • GitHub API data is fetched through your server — no client-side token exposure
  • Graph data stored in a local NebulaGraph instance you control
  • Authentication via self-hosted Ory Kratos — no external auth provider
  • Secret validation modules run in a sandboxed WASM runtime
  • No data is sent anywhere outside your deployment
// 06

roadmap

what's next
// 07

faq

5 questions
what does it detect?
Social graph relationships (followers, orgs, contributions), git commit identities (authors, emails, PGP keys), and leaked secrets (AWS, GCP, Stripe, Slack — 45+ validators via WASM modules).
is it a CLI tool?
No — it's a self-hosted web platform. Go API, Rust workers, React frontend with real-time graph visualization via Sigma.js and NebulaGraph.
is it legal?
It only reads public GitHub data and public git history. Same data as git log and the GitHub API. No authentication bypass, no scraping beyond API rate limits.
can it validate found secrets?
Yes. 45+ WASM modules check secrets against live APIs (AWS STS, Stripe, Slack, Discord, OpenAI, etc.) to confirm if they're still active.
what's the stack?
Go API (Fiber), Rust workers (Tokio), React frontend (Sigma.js), NebulaGraph (graph DB), Redis (queues), PostgreSQL, Ory Kratos (auth). Protobuf for inter-service messaging.
> ESC
↑↓ navigate select esc close