live · scanning repos
Scanrepo
github.com
github.com / brunolee-GIT

brunolee-GIT/W3M0dP4tch32

4 files·commit c07174e·scanned 3h ago·cached ✓
0/100
SAFE
No malicious patterns found. Repo signals are consistent with a legitimate project.
verdict accurate?
threat-state: safelive

FINDINGS ░▒▓

CLEAN
No malicious patterns found across 0/4 content-scanned files.
Static analysis only — treat as “nothing found”, not a guarantee.

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.

0 files scanned @ c07174e | 10/30/2026 | heuristic scan — always review manually

risk by category
code execution0
network & exfiltration0
file system access0
obfuscation0
supply chain0
owasp / injection0
telemetry
files 0/4rules hit 0engine v10commit c07174e

github

brunolee-GIT/W3M0dP4tch32

W3M0dP4tch32 t0 P4tch W3M0d

980
62
1161d
4 files
0 scanned(0%)
c07174e

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.

SAFE (0/100) — brunolee-GIT/W3M0dP4tch32 — ScanRepo