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

alexbelgium/hassio-addons

https://github.com/alexbelgium/hassio-addons · scanned 2026-06-05 19:33 UTC (4 days, 16 hours ago) · 10 languages

495 raw signals (39 security + 456 graph) 11/13 scanners ran 79th percentile · Python · tiny (<2K LoC) System graph score 66 (higher by 7)

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

Complete repo analysis

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

JSON
Combined
67.0
/100
Security checks
68
14 findings
System graph
66
100.0% cov · 175 findings
Critical
8
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 30.0 0.15 4.50
security_score 100.0 0.25 25.00
testing_score 70.0 0.20 14.00
documentation_score 75.0 0.15 11.25
practices_score 72.0 0.15 10.80
code_quality 80.0 0.10 8.00
Overall 1.00 73.5
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 8 High 3 Medium 147 Low 19 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 14 System graph 175 Crowd 0 Layer: Quality 14 Software 3 Cicd 6 Api 1 Network 4 Hardware 151 Frontend 1 Security 9

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

#1
Possible secret in joplin/rootfs/etc/cont-init.d/99-run.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 joplin/rootfs/etc/cont-init.d/99-run.sh:117; move to env var / secrets manager.
joplin/rootfs/etc/cont-init.d/99-run.sh:117
#2
Possible secret in joplin/rootfs/etc/cont-init.d/99-run.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 joplin/rootfs/etc/cont-init.d/99-run.sh:136; move to env var / secrets manager.
joplin/rootfs/etc/cont-init.d/99-run.sh:136
#3
Possible secret in photoprism/rootfs/run.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 photoprism/rootfs/run.sh:61; move to env var / secrets manager.
photoprism/rootfs/run.sh:61
#4
Possible secret in photoprism/rootfs/etc/cont-init.d/99-run.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 photoprism/rootfs/etc/cont-init.d/99-run.sh:47; move to env var / secrets manager.
photoprism/rootfs/etc/cont-init.d/99-run.sh:47
#5
Possible secret in photoprism/rootfs/etc/cont-init.d/99-run.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 photoprism/rootfs/etc/cont-init.d/99-run.sh:149; move to env var / secrets manager.
photoprism/rootfs/etc/cont-init.d/99-run.sh:149
#6
Possible secret in postgres_15/rootfs/etc/cont-init.d/99-run.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 postgres_15/rootfs/etc/cont-init.d/99-run.sh:155; move to env var / secrets manager.
postgres_15/rootfs/etc/cont-init.d/99-run.sh:155
#7
Possible secret in postgres_15/rootfs/etc/cont-init.d/99-run.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 postgres_15/rootfs/etc/cont-init.d/99-run.sh:156; move to env var / secrets manager.
postgres_15/rootfs/etc/cont-init.d/99-run.sh:156
#8
Possible secret in immich/rootfs/etc/cont-init.d/99-run.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 immich/rootfs/etc/cont-init.d/99-run.sh:88; move to env var / secrets manager.
immich/rootfs/etc/cont-init.d/99-run.sh:88
#9
Possible secret in immich/rootfs/etc/cont-init.d/99-run.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 immich/rootfs/etc/cont-init.d/99-run.sh:91; move to env var / secrets manager.
immich/rootfs/etc/cont-init.d/99-run.sh:91
#10
Possible secret in immich/rootfs/etc/cont-init.d/99-run.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 immich/rootfs/etc/cont-init.d/99-run.sh:181; move to env var / secrets manager.
immich/rootfs/etc/cont-init.d/99-run.sh:181

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/c8a81978-840b-4407-a33e-14d56d62439c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c8a81978-840b-4407-a33e-14d56d62439c/

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.