live · scanning repos
Scanrepo
github.com
github.com / jforkster

jforkster/xliveless

C++·13 files·commit d34f77b·scanned 57m ago·cached ✓
4/100
SAFE
No malicious patterns found. Repo signals are consistent with a legitimate project.
verdict accurate?
threat-state: safelive

FINDINGS ░▒▓

infoSuspicious file in repoExecutable file (compile.bat) in repository_dist/compile.bat+2
infoSuspicious file in repoExecutable file (compile_with_trace.bat) in repository_dist/compile_with_trace.bat+2

Scores are heuristics. A “safe” verdict means no known-malicious patterns were found — clever malware can look boring. Wrong verdict? Flag it above; confirmed false positives become regression tests.

2 files scanned @ d34f77b | 9/25/2026 | heuristic scan — always review manually

risk by category
code execution0
network & exfiltration0
file system access0
obfuscation0
supply chain4
owasp / injection0
telemetry
files 2/13rules hit 2engine v6commit d34f77b

github

jforkster/xliveless

GitHub mirror of https://git.nick7.com/gta/xliveless

C++
19
2
2747d
13 files
2 scanned(15%)
d34f77b

architecture░▒▓

No architecture graph available. This usually happens when the repo contains no scannable JS/TS/Python files or only a single file was analyzed.