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.
Sign up free Scan another repo
78 of your 120 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 6.44s · analysis 13.61s · 13.0 MB · GitHub API rate-limit (preflight)

dusklinux/dusky

https://github.com/dusklinux/dusky · scanned 2026-06-05 12:49 UTC (5 days, 10 hours ago) · 10 languages

352 raw signals (110 security + 242 graph) 32nd percentile · Python · medium (20-100K LoC) System graph score 72 (lower by 30)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 10 hours ago · v2 · 145 actionable findings from 2 signal sources. 86 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
60.4
/100
Security checks
49
42 findings
System graph
72
88.9% cov · 103 findings
Critical
5
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 40.0 0.15 6.00
security_score 66.0 0.25 16.50
testing_score 0.0 0.20 0.00
documentation_score 81.0 0.15 12.15
practices_score 40.0 0.15 6.00
code_quality 10.8 0.10 1.08
Overall 1.00 41.7
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 5 High 15 Medium 39 Low 61 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 42 System graph 103 Crowd 0 Layer: Software 37 Security 16 Quality 74 Api 1 Network 15 Frontend 1 Cicd 1

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

#1
Possible secret in user_scripts/arch_iso_scripts/offline_iso/010_set_variables.sh
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in user_scripts/arch_iso_scripts/offline_iso/010_set_variables.sh:127; move to env var / secrets manager.
user_scripts/arch_iso_scripts/offline_iso/010_set_variables.sh:127
#2
Possible secret in user_scripts/arch_iso_scripts/offline_iso/010_set_variables.sh
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in user_scripts/arch_iso_scripts/offline_iso/010_set_variables.sh:137; move to env var / secrets manager.
user_scripts/arch_iso_scripts/offline_iso/010_set_variables.sh:137
#3
Possible secret in user_scripts/arch_iso_scripts/offline_iso/110_post_chroot.sh
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in user_scripts/arch_iso_scripts/offline_iso/110_post_chroot.sh:301; move to env var / secrets manager.
user_scripts/arch_iso_scripts/offline_iso/110_post_chroot.sh:301
#4
Possible secret in user_scripts/arch_iso_scripts/online/110_post_chroot.sh
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in user_scripts/arch_iso_scripts/online/110_post_chroot.sh:310; move to env var / secrets manager.
user_scripts/arch_iso_scripts/online/110_post_chroot.sh:310
#5
Insecure pattern 'eval_used' in user_scripts/tts_stt/old/parakeet/transcribe_parakeet.py:102
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
user_scripts/tts_stt/old/parakeet/transcribe_parakeet.py:102
#6
Insecure pattern 'eval_used' in user_scripts/tts_stt/old/parakeet/verson_2/transcribe_parakeet.py:94
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
user_scripts/tts_stt/old/parakeet/verson_2/transcribe_parakeet.py:94
#7
Insecure pattern 'eval_used' in user_scripts/tts_stt/old/parakeet/version_3/transcribe_parakeet.py:102
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
user_scripts/tts_stt/old/parakeet/version_3/transcribe_parakeet.py:102
#8
Insecure pattern 'eval_used' in user_scripts/tts_stt/old/parakeet/version_1.3/transcribe_parakeet.py:53
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
user_scripts/tts_stt/old/parakeet/version_1.3/transcribe_parakeet.py:53
#9
Insecure pattern 'eval_used' in user_scripts/hypr/monitor/screen_rotate.py:322
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
user_scripts/hypr/monitor/screen_rotate.py:322
#10
Privileged port 12 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in user_scripts/rofi/emoji.sh is a real port, change the binding to ≥1024 or run behind a proxy.
user_scripts/rofi/emoji.sh

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/030fee21-ee02-4cb9-b5ed-ef2cdb0d7e74/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/030fee21-ee02-4cb9-b5ed-ef2cdb0d7e74/

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.