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.
43 of your 67 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.44s · analysis 0.83s · 1.3 MB · GitHub API rate-limit (preflight)

hackingtool

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

154 findings (66 legacy + 88 scanner) 30th percentile · Python · small (2-20K LoC) Scanner says 75 (lower by 14)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 5 days ago · v2 · 110 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 55.0 0.15 8.25
security_score 90.4 0.25 22.60
testing_score 0.0 0.20 0.00
documentation_score 62.0 0.15 9.30
practices_score 85.0 0.15 12.75
code_quality 75.0 0.10 7.50
Overall 1.00 60.4
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Insecure pattern 'subprocess_shell_true' in install.py:119
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
install.py:119
#2
Insecure pattern 'subprocess_shell_true' in os_detect.py:130
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
os_detect.py:130
#3
Insecure pattern 'subprocess_shell_true' in tools/tool_manager.py:29
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
tools/tool_manager.py:29
#4
Insecure pattern 'weak_hash' in tools/others/hash_crack.py:12
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
tools/others/hash_crack.py:12
#5
Docker base image uses a mutable or implicit tag: kalilinux/kali-rolling:latest
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
Dockerfile:3
#6
Dockerfile runs as root: Dockerfile
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
#7
Very low test-to-source ratio
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity
#8
Network/subprocess call without timeout or try/except — install.py:91
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Add a `timeout=N` argument and wrap in `try/except` in install.py:91 to prevent hung calls.
#9
Network/subprocess call without timeout or try/except — os_detect.py:130
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Add a `timeout=N` argument and wrap in `try/except` in os_detect.py:130 to prevent hung calls.
#10
Network/subprocess call without timeout or try/except — tools/information_gathering.py:50
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Add a `timeout=N` argument and wrap in `try/except` in tools/information_gathering.py:50 to prevent hung calls.

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/f50c051f-a6b1-420d-86a0-2f826673808d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f50c051f-a6b1-420d-86a0-2f826673808d/

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.