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.

SveleOla/OLPR

https://github.com/SveleOla/OLPR · scanned 2026-06-16 00:26 UTC (2 months, 2 weeks ago)

41 raw signals (0 security + 41 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 40 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 92.0/100 with 88.9% coverage. It contains 223 nodes across 14 cross-layer flows, written primarily in mixed languages. Engine surfaced 41 findings — concentrated in quality (18), software (12), security (9). Risk profile is low: 0 critical, 0 high, 21 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 38 of 40 actionable findings. 41 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/static/app.js:48
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/static/docs.js:200
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/static/events.js:28
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/static/logg.js:87
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/static/settings.js:80
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/static/skilt_settings.js:244
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/static/statistikk.js:9
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — core/static/ukjente.js:22
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in core/static/app.js:74
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
core/static/app.js:74 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in core/static/docs.js:101
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
core/static/docs.js:101 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in core/static/events.js:36
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
core/static/events.js:36 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in core/static/logg.js:49
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
core/static/logg.js:49 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in core/static/settings.js:123
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
core/static/settings.js:123 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in core/static/skilt_settings.js:97
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
core/static/skilt_settings.js:97 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in core/static/statistikk.js:20
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
core/static/statistikk.js:20 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in core/static/ukjente.js:30
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
core/static/ukjente.js:30 Direct innerhtml assignment
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 15 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: core/olpr_core/config.py:load_skilt, core/olpr_core/bridge.py:load_kjente_skilt This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: deco
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/web.py:562
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/web.py:1173
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/web.py:1213
low System graph software Dead code conf 1.00 Possibly dead Python function: do_restart
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/web.py:965
low System graph software Dead code conf 1.00 Possibly dead Python function: lagre
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/bridge.py:373
low System graph software Dead code conf 1.00 Possibly dead Python function: load_today_lines
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/web.py:228
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/web.py:1130
low System graph software Dead code conf 1.00 Possibly dead Python function: prefetch_snapshot
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/bridge.py:191
low System graph software Dead code conf 1.00 Possibly dead Python function: prune_snapshots_worker
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/bridge.py:413
low System graph software Dead code conf 1.00 Possibly dead Python function: register_commit_hook
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/bridge.py:316
low System graph software Dead code conf 1.00 Possibly dead Python function: register_routes
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/web.py:554
low System graph software Dead code conf 1.00 Possibly dead Python function: shutdown
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
core/olpr_core/bridge.py:573
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph quality Integrity conf 1.00 Stub function `log_message` (body is just `pass`/`return`) — core/olpr_core/web.py:1130
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
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/ef22785e-301b-4001-bf8a-7e54c56827ea/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ef22785e-301b-4001-bf8a-7e54c56827ea/

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.