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

fediaFedia/Longhorn

Pascal·540 files·commit e524f99·scanned 2h ago·cached ✓
8/100
SAFE
No malicious patterns found. Repo signals are consistent with a legitimate project.
verdict accurate?
0% file coverage
threat-state: safelive

FINDINGS ░▒▓

infoSuspicious file in repoExecutable file (Config.exe) in repository@Resources/Config.exe+2
infoSuspicious file in repoExecutable file (ipconfig.bat) in repositoryParts/Network/ipconfig.bat+2
infoSuspicious file in repoExecutable file (ReserveScreenSpace.exe) in repositoryReserve Screen Space/Older AutoIt Code/ReserveScreenSpace.exe+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.

1 files scanned @ e524f99 | 9/25/2026 | heuristic scan — always review manually

risk by category
code execution0
network & exfiltration0
file system access0
obfuscation0
supply chain8
owasp / injection0
telemetry
files 1/540rules hit 3engine v6commit e524f99

github

fediaFedia/Longhorn

Pascal
38
2
1336d
540 files
1 scanned(0%)
e524f99

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.