/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

sherlock-project/sherlock

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T11:49:57.525Z

3mo ago

sherlock-project/sherlock

sherlock-project/sherlock is a Python OSINT tool for finding social media accounts by username across social networks. It is active, stable, and heavily forked/starred, with recent commits through 2026-03-30. The repo includes docs, tests, container tooling, and a packaged CLI entry point named `sherlock`.

Loading tags...

Stars74,282

Forks8,822

Default branchmaster

Last pushed2026-03-30T05:47:09Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork only if its larger custom site corpus and `maigret`-specific workflow are more valuable to you than staying current with upstream. For most adopters, upstream is the safer choice because this fork is very old and substantially behind.

Prefer upstream unless you explicitly need a frozen historical base. This fork offers no clear added capability, while its large lag makes it materially worse for current OSINT use.

Prefer upstream unless you explicitly need an older frozen copy; this fork adds no evident capabilities and is too far behind for normal use.

Prefer upstream unless you specifically need an archived 2020-era baseline. This fork shows no unique evolution and is too far behind for users who care about current OSINT coverage or ongoing compatibility.

Prefer upstream unless you explicitly need an old, untouched baseline. This fork offers no visible product upside and is materially behind current development.

Choose this fork only if the Discord-bot angle or custom Watson change is the point. For most adopters, upstream is the better base because it is much newer, actively maintained, and has far broader recent site/fix coverage.

Choose upstream unless you have a specific reason to stay on an older 2023 snapshot. This fork offers no visible functional advantage and is materially behind on maintenance and site coverage.

Prefer upstream unless you specifically need this old snapshot. This fork adds no visible functionality and is too far behind to be a good adoption base for normal OSINT use.

Prefer upstream unless you specifically need this exact older snapshot. This fork adds no evident capabilities, is materially behind, and is best treated as a stale mirror rather than a maintained alternative.

Prefer upstream unless you specifically need this exact snapshot. This fork adds no visible value over upstream and is materially behind ongoing fixes and site coverage.

Fork comparison

torerobo/maigret

38/100

stale

significant_divergence

Choose this fork only if its larger custom site corpus and `maigret`-specific workflow are more valuable to you than staying current with upstream. For most adopters, upstream is the safer choice because this fork is very old and substantially behind.

Likely purpose

A user would prefer this fork if they want the `maigret` branding, a much larger curated site database, and extra site-maintenance workflow around updating and organizing target sources, even at the cost of falling far behind upstream changes.

Best for

Operators who want a frozen, customized username-lookup fork and do not need current upstream fixes.; People building a niche internal OSINT workflow around a larger curated site list.; Maintainers who prefer starting from an older, simpler branch and are willing to carry their own updates.; Users who specifically want the `maigret` naming and dossier-oriented positioning.

Additional features

Expanded site corpus, including a large `maigret/resources/data.json` rewrite and added site-management content in `sites.md`.
A dedicated site update workflow via `update_site_data.py`.
Recursive-search documentation in `examples/recursive_search.md`, suggesting support for chaining or extending lookups beyond a single pass.
Renamed package/module layout from `sherlock` to `maigret`, indicating a fork-specific command and code identity.
Adds fork-specific behavior in `maigret/resources/data.json` and `sherlock/resources/data.json`.

Missing features

It is far behind upstream, so it likely lacks many later upstream fixes, site additions, and compatibility updates.
Upstream’s recent operational hardening and bug fixes, such as LinkedIn WAF handling and newer site regex fixes, are not present in this fork’s timeline.
The fork appears to have removed upstream-specific project framing and some repo hygiene files, including `CODE_OF_CONDUCT.md` and `site_list.py`.
Because the fork stopped in 2020, users should expect older packaging, docs, and test coverage than current upstream.
It trails upstream by 2302 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Much larger apparent target-site dataset than upstream's older snapshot.
Clearer emphasis on dossier-style username investigation and site curation.
Some added workflow docs and scripts make it more suited to maintaining a custom site list.
Low commit count since divergence means the fork is relatively simple to audit if you only need the frozen 2020 behavior.

Risks

Very stale codebase with a large upstream gap.
High chance of broken or outdated site logic compared with current social-network defenses.
Rebranding and rename increase migration friction for users or scripts expecting upstream `sherlock` paths.
Removed or missing upstream maintenance files suggest weaker project governance and contributor safeguards.

sherlock-project/sherlock · Discofork