Maigret
v0.6.6 open-sourceThe section your link pointed to isn't on Maigret's page any more, so we've brought you to the top.
Collect a dossier on a person by username from 3000+ sites
maigret --input-file ids.txt --html ./generate-usernames.py john.smith | maigret --input-file - --html maigret --input-file ids.txt ./generate-usernames.py john.smith | maigret --input-file - maigret --xmind <username> maigret 10001 --id-type qq_id maigret 2 --id-type bilibili_id maigret 10001 --id-type qq_id maigret 2 --id-type bilibili_id maigret 10001 --id-type qq_id maigret 2 --id-type bilibili_id maigret 10001 --id-type qq_id maigret 2 --id-type bilibili_id maigret johndoe --keywords hacker,security maigret johndoe --neo4j maigret johndoe --dns-resolver threaded pip install 'maigret[pdf]' maigret --tags crypto johndoe maigret <username> --json maigret --db-stats
Summary
Maigret is an open-source OSINTOSINTOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. command-line tool that builds a dossier on a person from a username alone, checking it against a large database of sites and pulling whatever profile data those pages expose, with no API keys required. It is run from the command line, with an optional Docker web image for self-hosted deployment, and can be scripted into automation pipelines as well as invoked as a library. It targets OSINT researchers and pentesters who need to map a person's footprint across social media, crypto, and other platforms from a single alias. It sits in the reconnaissance and username-enumeration space, extending searches with permutated username variants, Cloudflare-bypass mechanisms, and export to Neo4j for link analysis. First committed in 2020, it has 83 contributors and remains active, with over 500 commits and a release just 39 days ago.
Collect a dossier on a person by username from 3000+ sites
How Maigret helps
Which accounts across the internet belong to the same person as this username?
checks the alias against its full site database and returns every matching profile it finds, pulling whatever bio, avatar, or activity data those pages expose
Which crypto-related identities trace back to this alias?
filters its site database down to sites tagged crypto — ENS domains and similar blockchain identity lookups — and reports which ones resolve for the username
Are any of the matches actually a different person with the same name?
narrows results to profiles whose page text contains keywords you supply, so a common name can be filtered down to the account that is actually the target
How do I turn a list of discovered accounts into a link-analysis graph?
exports the findings as a Neo4j Cypher file, so the accounts and their relationships can be loaded straight into a graph database
Which sites are blocking this search outright?
flags sites it detects as Cloudflare-protected and routes those checks through a bypass mechanism, rather than silently returning them as not-found
What other usernames might the same person be using?
generates permutated variants of the given alias and searches those too, surfacing accounts registered under close variations of the original name
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for Maigret, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Maigret puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
25 entries
No entries match these filters.
- September 20263
- August 20266
- July 20268
- May 20261
- April 20261
- August 20251
- September 20221
- January 20222
- February 20211
- January 20211
Project health
Issue, contributor and maintainer activity in soxoj/maigret, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 44 +32 vs prior 12 months
- Maintainers 2 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 21% of issues opened, last 12 months
- Median time to close 4.6 days first maintainer reply 2.1 days
- Open backlog 17 of 1,610 issues ever filed
- Issues opened / month 2 · 8 communitymaintainers
- Open backlog 17
- Contributors / month 6
- Commits / month 54
- Stars 37,760
- bugs 5%
- features 3%
- questions 0%
- other 92%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.