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

Scan timing: clone 4.26s · analysis 28.33s · 89.9 MB · GitHub API rate-limit (preflight)

nightscout/nocturne

https://github.com/nightscout/nocturne · scanned 2026-06-05 22:41 UTC (4 days, 7 hours ago) · 10 languages

458 raw signals (118 security + 340 graph) 11/13 scanners ran 33rd percentile · Csharp · huge (>500K LoC) System graph score 63 (higher by 12)

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

Complete repo analysis

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

JSON
Combined
71.4
/100
Security checks
80
50 findings
System graph
63
100.0% cov · 102 findings
Critical
6
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 65.0 0.15 9.75
security_score 100.0 0.25 25.00
testing_score 82.0 0.20 16.40
documentation_score 55.0 0.15 8.25
practices_score 71.0 0.15 10.65
code_quality 50.0 0.10 5.00
Overall 1.00 75.0
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 6 High 10 Medium 20 Low 77 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 50 System graph 102 Crowd 0 Layer: Cicd 19 Quality 48 Security 13 Software 55 Api 1 Frontend 13 Network 1 Hardware 2

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

#1
Possible secret in docs/postgres/container-init/00-init.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 docs/postgres/container-init/00-init.sh:44; move to env var / secrets manager.
docs/postgres/container-init/00-init.sh:44
#2
Possible secret in docs/postgres/container-init/00-init.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 docs/postgres/container-init/00-init.sh:45; move to env var / secrets manager.
docs/postgres/container-init/00-init.sh:45
#3
Possible secret in docs/postgres/container-init/00-init.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 docs/postgres/container-init/00-init.sh:46; move to env var / secrets manager.
docs/postgres/container-init/00-init.sh:46
#4
Possible secret in deploy/docker-compose/init/00-init.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 deploy/docker-compose/init/00-init.sh:44; move to env var / secrets manager.
deploy/docker-compose/init/00-init.sh:44
#5
Possible secret in deploy/docker-compose/init/00-init.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 deploy/docker-compose/init/00-init.sh:45; move to env var / secrets manager.
deploy/docker-compose/init/00-init.sh:45
#6
Possible secret in deploy/docker-compose/init/00-init.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 deploy/docker-compose/init/00-init.sh:46; move to env var / secrets manager.
deploy/docker-compose/init/00-init.sh:46
#7
Possible secret in deploy/portainer/docker-compose.yaml
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 deploy/portainer/docker-compose.yaml:203; move to env var / secrets manager.
deploy/portainer/docker-compose.yaml:203
#8
Possible secret in deploy/portainer/docker-compose.yaml
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 deploy/portainer/docker-compose.yaml:204; move to env var / secrets manager.
deploy/portainer/docker-compose.yaml:204
#9
Possible secret in deploy/portainer/docker-compose.yaml
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 deploy/portainer/docker-compose.yaml:205; move to env var / secrets manager.
deploy/portainer/docker-compose.yaml:205
#10
Possible secret in deploy/portainer/docker-compose.yaml
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 deploy/portainer/docker-compose.yaml:207; move to env var / secrets manager.
deploy/portainer/docker-compose.yaml:207

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/9287f0ec-2794-49f7-bdc4-6dd3062629db/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/9287f0ec-2794-49f7-bdc4-6dd3062629db/

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.