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.

wpdlf/local-pdf-analyzer

https://github.com/wpdlf/local-pdf-analyzer · scanned 2026-06-16 01:00 UTC (2 months, 1 week ago)

55 raw signals (0 security + 55 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 55 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 7 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 55 Crowd 0 Layer: Frontend 7 Security 3 Cicd 1 Quality 40 Api 4

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 66.1/100 with 100.0% coverage. It contains 609 nodes across 7 cross-layer flows, written primarily in mixed languages. Engine surfaced 55 findings — concentrated in quality (40), frontend (7), api (4). Risk profile is high: 0 critical, 3 high, 7 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 17 of 55 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 api Wiring conf 1.00 Dangling fetch: GET http://localhost:11434/api/version (e2e/collection-phase3.spec.ts:29)

`e2e/collection-phase3.spec.ts:29` calls `GET http://localhost:11434/api/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:11434/api/version` If this points at an external API, prefix it with `…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:11434/api/version (e2e/collection.spec.ts:30)

`e2e/collection.spec.ts:30` calls `GET http://localhost:11434/api/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:11434/api/version` If this points at an external API, prefix it with `https:/…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:11434/api/version (e2e/tabs.spec.ts:114)

`e2e/tabs.spec.ts:114` calls `GET http://localhost:11434/api/version` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:11434/api/version` If this points at an external API, prefix it with `https://` so…

Dangling fetchFetch

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/renderer/lib/safe-markdown.tsx:133

Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html

Fq dangerous html

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/components/PdfViewer.tsx:270

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

src/renderer/components/PdfViewer.tsx:270 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in src/main/ollama-manager.ts:1

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

src/main/ollama-manager.ts:1 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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 25 placeholder/mock markers across 9 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 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 — src/main/index.ts:169

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/ollama-manager.ts:118

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/lib/__tests__/csp-inline-hash.test.ts:7

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 api Wiring conf 1.00 Unused endpoint: GET

`src/renderer/lib/pdf-parser.ts` declares `GET ` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph quality Complexity conf 1.00 Very large file: src/main/ai-service.ts (1809 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/lib/use-qa.ts (1157 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/9e538277-358d-4379-8c6d-9644d9838687/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9e538277-358d-4379-8c6d-9644d9838687/

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.