github.com / Qervas
Qervas/ remote-grok-build
PowerShell·20 files·commit cd11941·scanned 2h ago·cached ✓
12/100
LOW RISK
Minor findings consistent with the project type. Nothing reachable from install hooks.
verdict accurate?
Created 8 days ago
No stars or forks
Created 8 days ago
No community activity
threat-state: lowlive
FINDINGS ░▒▓
infoSuspicious file in repoExecutable file (grok-after-turn.ps1) in repositoryhelpers/grok-after-turn.ps1+2
infoSuspicious file in repoExecutable file (grok-interrupt.ps1) in repositoryhelpers/grok-interrupt.ps1+2
infoSuspicious file in repoExecutable file (grok-mission-control.ps1) in repositoryhelpers/grok-mission-control.ps1+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 @ cd11941 | 9/25/2026 | heuristic scan — always review manually
risk by category
code execution0
network & exfiltration0
file system access0
obfuscation0
supply chain9
owasp / injection0
telemetry
files 2/20rules hit 4engine v6commit cd11941
github
Qervas/remote-grok-build
Grok Bot Agent Plugin: bridge chat to local Grok Build on a linked PC (mission control, streaming, optional workers/RGB channel).
0
0
8d
20 files
2 scanned(10%)
cd11941
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.