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

RumbleCrumbleRS/JellyPlug-Tizen

https://github.com/RumbleCrumbleRS/JellyPlug-Tizen · scanned 2026-06-15 23:57 UTC (2 months, 3 weeks ago)

124 raw signals (0 security + 124 graph)

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

Complete repo analysis

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

JSON
Combined
88.4
/100
Security checks
88
0 findings
System graph
88
66.7% cov · 121 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 24 Medium 33 Low 17 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 121 Crowd 0 Layer: Frontend 6 Security 40 Cicd 2 Quality 73
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 88.4/100 with 66.7% coverage. It contains 1042 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 124 findings — concentrated in quality (76), security (40), frontend (6). Risk profile is high: 0 critical, 24 high, 33 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 53 of 121 actionable findings. 124 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.

high System graph security security conf 1.00 Insecure pattern 'new_function_used' in packages/shell-tizen-bootstrap/src/boot-shell.min.js:198
Found a known-risky pattern (new_function_used). Review and replace if possible.
packages/shell-tizen-bootstrap/src/boot-shell.min.js:198 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in packages/shell-tizen-bootstrap/src/boot-shell.src.js:865
Found a known-risky pattern (new_function_used). Review and replace if possible.
packages/shell-tizen-bootstrap/src/boot-shell.src.js:865 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in packages/shell-tizen-bootstrap/src/index.html:202
Found a known-risky pattern (new_function_used). Review and replace if possible.
packages/shell-tizen-bootstrap/src/index.html:202 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in packages/shell-tizen/src/index.html:47
Found a known-risky pattern (new_function_used). Review and replace if possible.
packages/shell-tizen/src/index.html:47 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in packages/shell-tizen/src/shell.js:1029
Found a known-risky pattern (new_function_used). Review and replace if possible.
packages/shell-tizen/src/shell.js:1029 New function used
high System graph security security conf 1.00 Insecure pattern 'new_function_used' in packages/shell-tizen/src/shell.min.js:209
Found a known-risky pattern (new_function_used). Review and replace if possible.
packages/shell-tizen/src/shell.min.js:209 New function used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — packages/shell-tizen-bootstrap/src/boot-shell.min.js:198
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 — packages/shell-tizen-bootstrap/src/boot-shell.src.js:281
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 — packages/shell-tizen/scripts/babel-preload.test.cjs:194
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 — packages/shell-tizen/scripts/creds-guard.test.cjs:510
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 — packages/shell-tizen/scripts/foreign-origin-passthrough.test.cjs:11
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 — packages/shell-tizen/scripts/https-certificates.test.cjs:126
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 — packages/shell-tizen/scripts/network-error-recovery.test.cjs:204
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 — packages/shell-tizen/scripts/seed-injection.test.cjs:518
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 — packages/shell-tizen/src/shell.js:32
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 — packages/shell-tizen/src/shell.min.js:209
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/bootstrap-sign.yml CI/CD securitySupply chainGithub actions
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-tizen.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/shell-tizen-bootstrap/src/boot-shell.min.js:435
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/shell-tizen-bootstrap/src/boot-shell.min.js:435 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/shell-tizen-bootstrap/src/boot-shell.src.js:2117
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/shell-tizen-bootstrap/src/boot-shell.src.js:2117 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/shell-tizen/src/shell.js:2649
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/shell-tizen/src/shell.js:2649 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in packages/shell-tizen/src/shell.min.js:213
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
packages/shell-tizen/src/shell.min.js:213 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in packages/shell-tizen-bootstrap/src/boot-shell.min.js:435
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
packages/shell-tizen-bootstrap/src/boot-shell.min.js:435 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in packages/shell-tizen-bootstrap/src/boot-shell.src.js:3430
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
packages/shell-tizen-bootstrap/src/boot-shell.src.js:3430 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in packages/shell-tizen/src/shell.js:4149
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
packages/shell-tizen/src/shell.js:4149 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in packages/shell-tizen/src/shell.min.js:213
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
packages/shell-tizen/src/shell.min.js:213 Domparser html parse
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — packages/shell-tizen-bootstrap/scripts/build_boot_shell.py:77
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — packages/shell-tizen-bootstrap/scripts/build_bootstrap.py:194
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — packages/shell-tizen-bootstrap/scripts/verify_boot_shell_src.py:76
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — packages/shell-tizen/scripts/build_shell_min.py:92
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — packages/shell-tizen/scripts/verify_shell_src.py:84
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 60 placeholder/mock markers across 23 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated repo pattern
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 227 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 security security conf 1.00 Insecure pattern 'document_write' in packages/shell-tizen-bootstrap/src/boot-shell.min.js:435
Found a known-risky pattern (document_write). Review and replace if possible.
packages/shell-tizen-bootstrap/src/boot-shell.min.js:435 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in packages/shell-tizen-bootstrap/src/boot-shell.src.js:3425
Found a known-risky pattern (document_write). Review and replace if possible.
packages/shell-tizen-bootstrap/src/boot-shell.src.js:3425 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in packages/shell-tizen/src/shell.min.js:213
Found a known-risky pattern (document_write). Review and replace if possible.
packages/shell-tizen/src/shell.min.js:213 Document write
low System graph security security conf 1.00 Insecure pattern 'document_write' in release-artifacts/bootstrap/v2.0.1/README.md:27
Found a known-risky pattern (document_write). Review and replace if possible.
release-artifacts/bootstrap/v2.0.1/README.md:27 Document write
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: packages/shell-tizen/scripts/verify_shell_src.py:resolve_esbuild, packages/shell-tizen-bootstrap/scripts/verify_boot_shell_src.py:resolve_esbuild This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code…
4 occurrences
repo-level (4 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 quality Integrity conf 1.00 Old/deprecated-named symbol `JellyfinShellBootstrap_v2` in packages/server-shell-drop/scripts/emit_manifest.py:11
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 — packages/shell-tizen-bootstrap/src/boot-shell.min.js:435
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 — packages/shell-tizen-bootstrap/src/boot-shell.src.js:2763
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 — packages/shell-tizen/scripts/fixtures/tizen-stub.js:39
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 — packages/shell-tizen/src/shell.js:3496
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 — packages/shell-tizen/src/shell.min.js:213
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: packages/shell-tizen-bootstrap/src/boot-shell.src.js (3535 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: packages/shell-tizen/src/shell.js (4369 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/cf0f8777-b5a3-4d33-97ae-66b2ec4b988c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/cf0f8777-b5a3-4d33-97ae-66b2ec4b988c/

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.