Username checking without the Python soap opera
GoSearch is a username checker written in Go. You download one binary, or you build one, you point it at a handle, and it tests a few hundred sites for a matching profile URL. Functionally it sits next to Sherlock: public pages, existence rules, a printed list of hits. It does not read minds, and it does not become more accurate because the download was a single file.
There are three reasons it is in the twelve, and none of them is "it finds the truth Sherlock missed".
First, a single binary is kinder on a locked-down Windows or Mac machine where pipx is a fight with an administrator who has already said no. Second, the project has been actively maintained, unlike several username tools that were cut from this course for going quiet. Third, comparing two tools on the same handle is how you learn that FOUND is a vote. Votes can be wrong in unison.
The Consensus snapshot used for this course put GoSearch at a few hundred sites, not Maigret's thousands. Fewer hits than Maigret is the normal outcome, not a sign you broke it. Quote a site count in a report only after you have read the README for the version you ran. This paragraph will go stale. The binary's own documentation will not, if you bother to open it.
The licence is GPL-3.0. Running it yourself, unmodified, to study your own handle, is the use this lesson describes. If you later give someone else a modified binary, GPL-3.0 expects you to offer them the corresponding source. "I found a build on a forum" is not the interesting part of that sentence. Shipping code you cannot hand over the source for is how a tidy install becomes a licensing mess. Using the upstream release, as a learner, does not require you to solve that today. It requires you not to pretend the licence is MIT.
If your laptop treats Python like a contagious disease, GoSearch is the spare key. The spare key still opens the wrong doors.