GhostTrack

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

8 of your 14 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.24s · analysis 0.12s · 0.2 MB · GitHub API rate-limit (preflight)

https://github.com/HunxByts/GhostTrack.git · scanned 2026-05-24 01:22 UTC (1 week, 5 days ago) · 10 languages

29 findings (12 legacy + 17 scanner) 57th percentile · Python · tiny (<2K LoC) Scanner says 84 (lower by 17)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 5 days ago · v2 · last Δ +1.8 (diff) · 20 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	30.0	0.15	4.50
`security_score`	100.0	0.25	25.00
`testing_score`	70.0	0.20	14.00
`documentation_score`	40.0	0.15	6.00
`practices_score`	72.0	0.15	10.80
`code_quality`	70.0	0.10	7.00
Overall		1.00	67.3

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 7 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 12 9-layer 8 Crowd 0 Layer: Software 3 Quality 13 Api 1 Frontend 1 Security 1 Cicd 1

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 9 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

9 matching findings on this repo

medium Bare except continues silently GhostTR.py:159
low [COMP001] High cognitive complexity: Function `call_option` has cognitive compl… GhostTR.py:219
info [MINED067] Python Requests No Timeout: requests.get/post/etc. without timeout= … GhostTR.py:45
info [MINED064] Python Input Call: input() blocks for stdin. Inappropriate in servic… GhostTR.py:42
info [MINED043] Http Not Https: Hardcoded http:// (not localhost) for endpoints that… GhostTR.py:45
high [MINED036] Python Os System Call: os.system() invokes shell with no escaping. GhostTR.py:213
high [MINED006] Overcatch Baseexception: except BaseException: ... — prevents Ctrl+C… GhostTR.py:239
high [SEC078] Python: requests without timeout: requests.get/post without a timeout … GhostTR.py:45
medium Network/subprocess call without timeout or try/except — GhostTR.py:45

View all fragile runtime findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/27e5b881-b7f1-42d2-9f3e-16acbe153f37/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/27e5b881-b7f1-42d2-9f3e-16acbe153f37/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.