ibnaleem/gosearch

🔍 Search anyone's digital footprint across 300+ websites

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 19th, 2026
Created on November 9th, 2024
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 326
Total Stargazers: 3,663 (+0)
Total Subscribers: 36 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.2 hours
Mean response time: 3.2 days
90th percentile: 9.0 days
Tracked items: 55

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 519 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • false positive (33)
  • bug (10)
  • P2 (3)
  • enhancement (3)
  • environment (3)
  • P3 (2)
  • build (2)
  • data.json (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

GoSearch is an OSINT tool that searches for a person's digital footprint across hundreds of websites and leaked credential databases.

The tool addresses the time-consuming manual process of checking multiple platforms for a username by leveraging concurrent requests to automate searches across websites. Beyond website searches, it integrates with multiple breach databases including HudsonRock's Cybercrime Intelligence API for leaked credentials, ProxyNova's Combination Of Many Breaches API covering billions of compromised accounts, and BreachDirectory.org for additional breach data when an API key is provided. The tool was created as a Sherlock alternative, designed to address limitations in that project while adding expanded functionality.

GoSearch suits security researchers, penetration testers, and red team operators conducting reconnaissance and information gathering. It works well for anyone needing to quickly identify where a username appears across the internet or whether credentials associated with a username have been compromised in known breaches. The project explicitly positions itself as an alternative to Sherlock, offering broader coverage and additional breach database integration.

The project relies heavily on community contributions as stated in its README. Development activity shows consistent recent commits and regular weekly activity. The tool is written in Go and installable via standard Go tooling. A notable constraint exists for users on 32-bit architecture, which requires using a separate branch due to build incompatibilities on that platform.