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

thomasnrs/Lumi_Agent

https://github.com/thomasnrs/Lumi_Agent · scanned 2026-06-16 00:35 UTC (2 months, 2 weeks ago)

38 raw signals (0 security + 38 graph)

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

Complete repo analysis

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

JSON
Combined
85.2
/100
Security checks
85
0 findings
System graph
85
88.9% cov · 38 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 1 Medium 20 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 38 Crowd 0 Layer: Frontend 5 Security 16 Cicd 1 Quality 16
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 85.2/100 with 88.9% coverage. It contains 393 nodes across 2 cross-layer flows, written primarily in mixed languages. Engine surfaced 38 findings — concentrated in security (16), quality (16), frontend (5). Risk profile is high: 0 critical, 1 high, 20 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 33 of 38 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security security conf 1.00 Insecure pattern 'new_function_used' in scripts/dist.js:120
Found a known-risky pattern (new_function_used). Review and replace if possible.
scripts/dist.js:120 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/main/main.js:502
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 Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
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 cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/release.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/main.js:1638
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/main.js:1638 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/_chrome.js:129
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/_chrome.js:129 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/agents.html:193
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/agents.html:193 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/animations.html:117
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/animations.html:117 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/chat.html:1469
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/chat.html:1469 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/ctxmenu.html:100
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/ctxmenu.html:100 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/gallery.html:190
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/gallery.html:190 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/imagegen.html:218
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/imagegen.html:218 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/mcp.html:140
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/mcp.html:140 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/memory.html:96
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/memory.html:96 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/wizard.html:192
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/wizard.html:192 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in src/renderer/pages/workspace.html:997
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/renderer/pages/workspace.html:997 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/dist.js:6
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/dist.js:6 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/main.js:14
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/main/main.js:14 Node child process
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 quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 8 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 19 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
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 quality Integrity conf 1.00 Old/deprecated-named symbol `eleven_multilingual_v2` in src/main/main.js:4321
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/dist.js:109
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/make-icon.js:105
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/rebuild-pty.js:21
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/main/main.js:34
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/renderer/main.js:278
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Complexity conf 1.00 Very large file: src/main/main.js (7642 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/renderer/main.js (2083 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/6ed93489-540a-4224-b582-49735a03fd17/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/6ed93489-540a-4224-b582-49735a03fd17/

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.