torerobo/maigret
stale
significant_divergence
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.
cyclopt/sherlock2
stale
significant_divergence
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.
TheYahya/sherlock
stale
significant_divergence
Prefer upstream unless you explicitly need an older frozen copy; this fork adds no evident capabilities and is too far behind for normal use.
omarkdev/sherlock-project-sherlock
stale
significant_divergence
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.
soxoj/sherlock
stale
significant_divergence
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.
ANG13T/sherlock
stale
significant_divergence
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.
Ethicalhackx/sherlock
stale
significant_divergence
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.
DevZenMaster/sherlock
stale
significant_divergence
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.