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

Scan timing: clone 13.96s · analysis 4.58s · 12.2 MB · GitHub preflight 430ms

boku7/Loki

https://github.com/boku7/Loki.git · scanned 2026-06-05 01:32 UTC (12 hours, 9 minutes ago) · 10 languages

63 findings (17 legacy + 46 scanner) 37th percentile · Javascript · small (2-20K LoC) Scanner says 98 (lower by 37)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 12 hours, 8 minutes ago · v2 · 40 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.5 0.25 22.62
testing_score 44.0 0.20 8.80
documentation_score 60.0 0.15 9.00
practices_score 40.0 0.15 6.00
code_quality 64.8 0.10 6.48
Overall 1.00 61.2
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
No auth library detected
GapSeverity.MEDIUM Layer.SECURITY score 0.338
Why: medium severity
#2
No CI/CD pipelines detected
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
#3
`fetch()` without try/.catch or AbortSignal — client/dashboard.js:378
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in client/dashboard.js:378, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#4
`fetch()` without try/.catch or AbortSignal — client/azure.js:526
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in client/azure.js:526, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#5
`fetch()` without try/.catch or AbortSignal — agent/renderer.js:20
GapSeverity.MEDIUM Layer.QUALITY score 0.225
Why: medium severity · crashes are likely without this
Fix: Wrap the `fetch(...)` in `try { ... } catch` in agent/renderer.js:20, OR pass `{ signal: AbortSignal.timeout(N) }` so the call cancels deterministically.
#6
Stray `console.log` in TS/JS — create_agent_payload.js:32
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in create_agent_payload.js:32.
#7
Stray `console.log` in TS/JS — client/dashboard.js:248
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in client/dashboard.js:248.
#8
Stray `console.log` in TS/JS — client/kernel.js:90
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in client/kernel.js:90.
#9
Stray `console.log` in TS/JS — client/azure.js:137
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in client/azure.js:137.
#10
Stray `console.log` in TS/JS — dev/COFFLoader/runBOF.js:87
GapSeverity.LOW Layer.FRONTEND score 0.170
Why: low severity · fix is short / mechanical
Fix: Delete or guard the `console.log` in dev/COFFLoader/runBOF.js:87.

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/bf7c966f-70bf-4cf3-a3c2-efbee0268295/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bf7c966f-70bf-4cf3-a3c2-efbee0268295/

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.