Should you use GhostTrack?
Choose GhostTrack as a source-reading exercise if you want to understand a simple interactive lookup script. Choose a more focused workflow when you need saved results or evidence you can defend. GhostTrack's phone option reads numbering metadata through phonenumbers rather than locating a handset.
The distinction matters because the README calls the menu a tracker. The supplied implementation parses a phone number and prints information such as region, carrier, timezone, validity and formatting. Those outputs do not establish where the phone is now.
What our sandbox established
In our run on September 30, 2026, at commit a5cb8ad, our sandbox recorded a successful 19-second install and a successful 7-second build step. The stored dependency summary reports 36 packages and 60 MB on disk.
Our harness records command outcomes through success flags, exit codes, elapsed time, timeout status and log tails. Both steps exited zero, but the build tail contains a SyntaxWarning about an invalid escape sequence. The supplied record does not identify the exact build command. It therefore supports a successful recorded build step, not a claim that we exercised the menu or completed a lookup.
Tests were skipped because the harness found no script. Skipped tests are not failed tests, and no passing-test count is available. Lookup accuracy, external-service availability and interactive operation remain untested in this evidence. This correction uses the existing run; it reports no new execution.
Pip-audit recorded zero advisories. The record has no scannedPackages field, so scan coverage is unknown. A zero advisory total does not establish that the script or its dependencies are secure.
The MrKeyoor testing methodology explains how the publisher records command outcomes and the limits of those observations. That page provides provenance context; its current procedure does not establish which procedure version the September run used.
What each lookup actually does
The main script sends IP queries to ipwho.is using plain HTTP. It prints response fields directly, including city, coordinates, network information and timezone. It converts latitude and longitude to integers for its map link, discarding their fractional parts. Treat the displayed location as an IP-data result, not proof of a person's address. Direct field access also means a missing response field can interrupt the lookup.
The phone option parses numbers with Indonesia as the default region and requests location descriptions in Indonesian. For readers elsewhere, an international country prefix avoids relying on that local-number assumption. The printed validity and location labels describe the parsed number; they do not confirm its owner or current position. Issue 130 reports incorrect phone-search information, but supplies no example that would let us reproduce or diagnose the complaint.
The username option requests a list of profile URLs sequentially. It records a URL as a match whenever the response status is 200, without checking the response body. Its requests have no explicit timeout. A returned URL therefore needs manual inspection, and even an existing profile does not establish that it belongs to the person you are researching.
Which alternatives fit the task?
For username searches that need spreadsheet output, Sherlock documents CSV and XLSX export options. Its README also documents request timeouts and site selection. These are concrete reasons to consider Sherlock as a replacement for GhostTrack's username branch; they do not prove that every returned account is correctly attributed.
PhoneInfoga is an option for configured phone-number research, but its repository says it is stable and unmaintained. Its README describes scanners, a browser interface and programmatic access, while explicitly ruling out real-time tracking and precise phone location. Consider it only if those investigation interfaces justify configuring the scanners and accepting the maintenance limitation. It replaces the phone-research branch, not GhostTrack's IP and username functions.
How to read the scores
These are editorial ratings, not benchmark results. The rubric is: 1 means major readiness gaps, 2 means limited supporting evidence with material gaps, 3 means adequate evidence for a defined task, 4 means strong evidence within the tested scope, and 5 means broad evidence across documented workflows. Each dimension uses its own evidence: setup uses command outcomes, documentation uses the supplied instructions, community uses support evidence, and maturity uses tests and operational safeguards.
Setup ease scores 4 for the successful install and build steps, with interactive operation still untested. Documentation scores 2 because the README gives launch instructions but does not explain the implementation's accuracy limits. Community scores 2 on limited support evidence; the supplied open accuracy report does not establish responsiveness or adoption. Maturity scores 1 because the recorded run skipped tests and the implementation relies on direct response-field access and username status checks without explicit request timeouts.
Before relying on a result, inspect the relevant lookup function and verify its output against the underlying source. Do not use the word "tracker" as evidence of live location.

