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.

Bidulkiya/ai-visor

https://github.com/Bidulkiya/ai-visor · scanned 2026-06-17 01:20 UTC (1 month, 2 weeks ago)

20 raw signals (0 security + 20 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -2.2 (diff) · 20 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 20 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 8 Low 8 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 20 Crowd 0 Layer: Frontend 7 Security 5 Quality 8

Exclude dismissed / FP Exclude test files

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 74.5/100 with 77.8% coverage. It contains 312 nodes across 1 cross-layer flows, written primarily in mixed languages. Engine surfaced 20 findings — concentrated in quality (8), frontend (7), security (5). Risk profile is high: 0 critical, 3 high, 8 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 19 of 20 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 'exec_used' in electron/preload.ts:36

Found a known-risky pattern (exec_used). Review and replace if possible.

electron/preload.ts:36 Exec used

high System graph security security conf 1.00 Insecure pattern 'exec_used' in renderer/src/memory/db.ts:31

Found a known-risky pattern (exec_used). Review and replace if possible.

renderer/src/memory/db.ts:31 Exec used

high System graph security security conf 1.00 Insecure pattern 'exec_used' in renderer/src/memory/ipcDriver.ts:13

Found a known-risky pattern (exec_used). Review and replace if possible.

renderer/src/memory/ipcDriver.ts:13 Exec used

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — electron/main.ts:50

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 — electron/tools/toolHost.ts:106

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 Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing license, ci, tests. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

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 'node_child_process' in electron/tools/toolHost.ts:10

Found a known-risky pattern (node_child_process). Review and replace if possible.

electron/tools/toolHost.ts:10 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 54 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 14 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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — renderer/src/core/affection.ts:218