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.

vishesh9131/markus

https://github.com/vishesh9131/markus · scanned 2026-06-16 00:51 UTC (2 months, 1 week ago)

25 raw signals (0 security + 25 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 25 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 15 Low 6 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 25 Crowd 0 Layer: Api 1 Frontend 2 Hardware 3 Security 7 Quality 12

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

Showing 22 of 25 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 vscode-markus/media/pdf.min.js:22

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

vscode-markus/media/pdf.min.js:22 New function used

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/app/layout.jsx:32

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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — vscode-markus/media/pdf.min.js:22

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 — web/app/studio/[ws]/page.jsx:134

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 — web/app/studio/page.jsx:125

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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/app/layout.jsx:32

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

web/app/layout.jsx:32 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in vscode-markus/media/viewer.js:63

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

vscode-markus/media/viewer.js:63 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in web/components/Studio.jsx:106

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

web/components/Studio.jsx:106 Local storage auth token

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in vscode-markus/extension.js:2

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

vscode-markus/extension.js:2 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in web/app/api/compile/route.js:1

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

web/app/api/compile/route.js:1 Node child process

medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in web/app/api/health/route.js:1

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

web/app/api/health/route.js:1 Node child process

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — vscode-markus/scripts/bundle-compiler.py:39

`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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 13 placeholder/mock markers across 6 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 Tests conf 1.00 Very low test-to-source ratio

6 test file(s) for 66 source file(s) (ratio 0.09). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Integrity conf 1.00 9 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `COMPILE_ALLOW_ORIGIN`, `COMPILE_MAX_CONCURRENT`, `COMPILE_RATE_LIMIT`, `LOCALAPPDATA`, `MARKUS_BIN`, `MARKUS_MAX_SECONDS`, `MARKUS_SANDBOX`, `MARKUS_TEX_BIN` + 1 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't bre…

config drift

low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

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

Found 10 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-bookworm-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

Dockerfile:4 containersPinned dependencies

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 — vscode-markus/media/pdf.min.js:22

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

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/d79f4a8d-2360-4902-8201-6c4eabd7bfc9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d79f4a8d-2360-4902-8201-6c4eabd7bfc9/

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.