nightscout/nocturne

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.

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)

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

100.0% cov · 102 findings

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

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `isLegacy` in src/Web/packages/app/src/lib/api/gene…

View all legacy markers findings →

Commented-out code 13 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (6 lines) in src/Web/remote-codegen.config.ts:17
info Commented-code block (5 lines) in src/Web/packages/bot/src/commands/alerts.ts:9
info Commented-code block (7 lines) in src/Web/packages/app/vite.config.ts:10
info Commented-code block (5 lines) in src/Web/packages/app/src/hooks.server.ts:16
info Commented-code block (5 lines) in src/Web/packages/app/src/lib/components/dashb…
info Commented-code block (6 lines) in src/Web/packages/app/src/lib/hooks/dialog-his…
info Commented-code block (8 lines) in src/Web/packages/app/src/lib/server/bot/index…
info Commented-code block (5 lines) in src/Web/packages/app/src/lib/forms/form-guard…
info Commented-code block (5 lines) in src/Web/packages/app/src/routes/api/v4/webhoo…
info Commented-code block (6 lines) in src/Web/packages/app/src/routes/(unauthentica…
info Commented-code block (6 lines) in src/Web/packages/cms/src/lib/components/edra/…
info Commented-code block (13 lines) in src/Web/packages/cms/src/lib/components/edra…

View all commented-out code findings →

Config drift 17 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

12 matching findings on this repo

low File has no detected symbols: src/Web/remote-codegen.config.ts
low File has no detected symbols: src/Web/packages/glucose-chart/svelte.config.js
low File has no detected symbols: src/Web/packages/ui/svelte.config.js
low File has no detected symbols: src/Web/packages/app/vitest.browser.config.ts
low File has no detected symbols: src/Web/packages/app/playwright.config.ts
low File has no detected symbols: src/Web/packages/app/vite.config.ts
low File has no detected symbols: src/Web/packages/app/svelte.config.js
low File has no detected symbols: src/Web/packages/app/eslint.config.js
low File has no detected symbols: src/Web/packages/app/wuchale.config.js
low File has no detected symbols: src/Web/packages/app/vitest.config.ts
low File has no detected symbols: src/Web/packages/app/src/lib/config/constants.ts
low File has no detected symbols: src/Web/packages/app/src/lib/components/settings/…

View all config drift findings →

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.