mrkeyoor.comAsk

HunxByts/GhostTracktested 30 Sept 2026commit a5cb8ad

GhostTrack review

GhostTrack is suitable for studying a small Python lookup script, but our sandbox evidence does not establish reliable investigative results.

  • Build 7 s
19 sto install
  • 36 packages
Dev Toolsevaluationupdated 01 Nov 2026
+108stars / 7d

Use GhostTrack to study a small Python lookup script; avoid it if you need live phone location or verified investigative results. GhostTrack's phone option reads numbering metadata through phonenumbers rather than locating a handset. Its other menu options request IP information, show your public IP, and check username URLs.

Verdict

GhostTrack is suitable for studying a small Python lookup script, but our sandbox evidence does not establish reliable investigative results. Our run at commit a5cb8ad on September 30, 2026, recorded installation in 19 seconds and a build step in 7 seconds; tests were skipped. Use Sherlock when documented username export options matter. Consider PhoneInfoga for configured phone research only with its explicit unmaintained status in view. Neither GhostTrack's phone metadata nor PhoneInfoga's documented scope provides live phone location.

We ran it

Lab card: what happened when we ran GhostTrack
Lab card from our sandbox run
Screenshot of GhostTrack (github.com/HunxByts/GhostTrack)
github.com/HunxByts/GhostTrack
Install✓ · 19s36 packages · 60 MB
Build✓ · 7s
Testsn/ano test script
Known vulns0(pip-audit)
Repo8 files~316 lines of source · 0.2 MB · 0 CI workflows

Answers from our run

Does GhostTrack build from source?

Dependencies installed in 19 seconds (36 packages), and the build succeeded in 7 seconds. We cloned commit a5cb8ad into a clean Debian container with 3 CPUs and no project-specific setup.

Does GhostTrack have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does GhostTrack have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use GhostTrack?

Anyone who needs a phone's current location.

What are the alternatives to GhostTrack?

Sherlock, PhoneInfoga. GhostTrack is suitable for studying a small Python lookup script, but our sandbox evidence does not establish reliable investigative results.

Setup4/5Strong evidence within the recorded setup scope: installation took 19 seconds and the build step took 7 seconds. Interactive operation was not established.
Docs2/5The supplied README documents Linux and Termux installation and launch steps, but does not explain the lookup accuracy limits visible in the implementation.
Community2/5Supporting evidence is limited to the supplied public material, including an open accuracy complaint without a reproducible example. Responsiveness and adoption are not established.
Maturity1/5Major readiness gaps: tests were skipped for lack of a script, no CI workflow was detected, and the implementation uses direct response-field access and username requests without explicit timeouts.

Who it’s for

Python learners who want to inspect how a terminal menu connects several lookup methods.
Readers checking phone-number formatting who can account for the script's Indonesia default.
Users who will inspect the source and verify lookup results independently.

Who it’s NOT for

Anyone who needs a phone's current location.
Investigators who need confirmed account ownership from username results.
Workflows that require documented automation and export options.
Users who need demonstrated lookup accuracy: our sandbox record does not establish it.

Setup reality

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. These are separate command outcomes, not a combined installation time. The stored record reports 36 installed packages and a 60 MB dependency footprint.

The harness stores each step's success flag, exit code, duration and timeout status, plus a log tail. Both recorded commands exited zero. The build tail nevertheless contains a SyntaxWarning about an invalid escape sequence. The exact build command is not supplied, so this outcome does not establish that the interactive program or its lookup workflows worked.

Tests were skipped with the reason "no script". The detector also recorded no tests directory, Python test target or CI workflow. Pip-audit recorded zero advisories, but scan coverage is unknown because scannedPackages is absent. That result is not a security assessment.

The README documents Python 3 installation, installing requirements and launching GhostTR.py on Linux or Termux. Our recorded environment was a Python 3.12 Debian Bookworm sandbox with 3 CPUs and 8 GB of RAM; it does not establish Termux compatibility.

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.

Alternatives

ProjectWhat it isPick it when
Sherlock gh↗A dedicated username-search tool with documented CSV and XLSX exports, site selection and request timeouts.Choose it as a replacement for GhostTrack's username branch when you need those output and request controls; verify account ownership separately.
PhoneInfoga gh↗A phone-number investigation framework whose repository explicitly describes it as stable but unmaintained.Consider it for configured phone research with browser or programmatic interfaces, accepting the maintenance limitation. It cannot provide real-time tracking or precise phone location.

What people are saying

  1. [github-trending] HunxByts/GhostTrack

Sources

  1. GhostTrack repository and README
  2. GhostTrack main Python script
  3. Phone information accuracy report, issue 130
  4. Missing IP response field fix, pull request 119

More dev tools reviews