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

rbcodelabs/obsidian-claude-threads

https://github.com/rbcodelabs/obsidian-claude-threads · scanned 2026-06-15 23:47 UTC (2 months, 3 weeks ago)

46 raw signals (0 security + 46 graph)

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

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 43 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
59.1
/100
Security checks
59
0 findings
System graph
59
77.8% cov · 43 findings
Critical
1
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 1 High 2 Medium 14 Low 13 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 43 Crowd 0 Layer: Frontend 6 Security 10 Cicd 2 Quality 25
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 59.1/100 with 77.8% coverage. It contains 588 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 46 findings — concentrated in quality (25), security (10), frontend (6). Risk profile is high: 1 critical, 2 high, 14 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 28 of 43 actionable findings. 46 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 'exec_used' in src/AgentDashboard.ts:444
Found a known-risky pattern (exec_used). Review and replace if possible.
src/AgentDashboard.ts:444 Exec used
high System graph security security conf 1.00 Insecure pattern 'exec_used' in src/KanbanView.ts:521
Found a known-risky pattern (exec_used). Review and replace if possible.
src/KanbanView.ts:521 Exec used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — relay/src/index.ts:16
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 — relay/src/RoomDO.ts:16
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 — relay/test/room.test.ts:257
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 — test/harness/obsidian-mock.ts:662
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 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/stt.ts:47
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
src/stt.ts:47 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/AgentDashboard.ts:440
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/AgentDashboard.ts:440 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/KanbanView.ts:517
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/KanbanView.ts:517 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/ObsidianTools.ts:12
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/ObsidianTools.ts:12 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/SkillsManagerView.ts:863
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/SkillsManagerView.ts:863 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/WakeLockService.ts:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
src/WakeLockService.ts:1 Node child process
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 25 placeholder/mock markers across 10 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 17 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 cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 4 locations
.github/workflows/ci.yml:16, 19 (2 hits)
.github/workflows/release.yml:17, 20 (2 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `acmeOld` in test/unit/kanban-folder-grouping.test.ts:121
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/seed-kanban-testvault.ts:43
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/logger.ts:20
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.ts:572
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 — test/unit/bundle-safety.test.ts:146
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 — test/unit/snapshot-completeness.test.ts:252
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: screenshots/src/ClaudeThreadsShots.tsx (1238 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/main.ts (1290 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/ObsidianTools.ts (1867 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/ThreadsView.ts (3165 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/d6050101-5f10-4343-89db-c5c039248a7c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d6050101-5f10-4343-89db-c5c039248a7c/

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.