ulsklyc/oikos

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.

45 of your 162 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 11.38s · analysis 9.13s · 24.1 MB · GitHub API rate-limit (preflight)

https://github.com/ulsklyc/oikos · scanned 2026-06-05 16:59 UTC (5 days ago) · 10 languages

526 raw signals (156 security + 370 graph) 48th percentile · Javascript · medium (20-100K LoC) System graph score 54 (higher by 13)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days ago · v2 · 250 actionable findings from 2 signal sources. 91 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 · 154 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	75.0	0.15	11.25
`security_score`	28.2	0.25	7.05
`testing_score`	90.0	0.20	18.00
`documentation_score`	94.6	0.15	14.19
`practices_score`	84.0	0.15	12.60
`code_quality`	43.9	0.10	4.39
Overall		1.00	67.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 22 High 67 Medium 19 Low 114 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 96 System graph 154 Crowd 0 Layer: Quality 75 Security 59 Cicd 12 Software 21 Frontend 26 Network 1 Hardware 3 Api 53

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.

Commented-out code 16 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 (5 lines) in test/test-dashboard.js:284
info Commented-code block (7 lines) in test/test-google-calendar.js:159
info Commented-code block (5 lines) in server/auth.js:42
info Commented-code block (6 lines) in server/index.js:85
info Commented-code block (5 lines) in server/routes/shopping.js:33
info Commented-code block (5 lines) in server/routes/preferences.js:148
info Commented-code block (7 lines) in server/routes/dashboard.js:54
info Commented-code block (6 lines) in server/routes/weather.js:29
info Commented-code block (6 lines) in server/routes/tasks.js:108
info Commented-code block (6 lines) in server/routes/reminders.js:18
info Commented-code block (8 lines) in server/routes/calendar.js:203
info Commented-code block (6 lines) in server/services/calendar-events.js:102

View all commented-out code findings →

Config drift 2 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.

2 matching findings on this repo

high Dangling fetch: GET /api/v1/auth/oidc/config (public/pages/login.js:132)
low Unused endpoint: GET /oidc/config

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/c293919d-235d-4152-bd13-8c803fa69eb1/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c293919d-235d-4152-bd13-8c803fa69eb1/

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.