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
56 of your 113 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 20.63s · analysis 6.35s · 30.6 MB · GitHub preflight 135ms

marktext/marktext

https://github.com/marktext/marktext · scanned 2026-06-05 09:59 UTC (5 days, 16 hours ago) · 10 languages

689 raw signals (95 security + 594 graph) 11/13 scanners ran 75th percentile · Typescript · large (100-500K LoC) System graph score 67 (higher by 14)

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

Complete repo analysis

Last scanned 5 days, 16 hours ago · v2 · 307 actionable findings from 2 signal sources. 85 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
73.8
/100
Security checks
80
25 findings
System graph
67
100.0% cov · 282 findings
Critical
1
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 84.0 0.20 16.80
documentation_score 63.0 0.15 9.45
practices_score 87.0 0.15 13.05
code_quality 80.0 0.10 8.00
Overall 1.00 81.3
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 2 Medium 10 Low 80 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 25 System graph 282 Crowd 0 Layer: Security 10 Quality 142 Cicd 6 Software 54 Api 1 Frontend 94

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 121 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
12 matching findings on this repo
  • info Commented-code block (5 lines) in eslint.config.js:26
  • info Commented-code block (6 lines) in scripts/thirdPartyChecker.ts:8
  • info Commented-code block (8 lines) in packages/muya/vite.config.ts:28
  • info Commented-code block (6 lines) in packages/muya/vitest.spec.config.ts:3
  • info Commented-code block (6 lines) in packages/muya/test/spec/runner.spec.ts:1
  • info Commented-code block (5 lines) in packages/muya/test/spec/roundTrip.spec.ts:10
  • info Commented-code block (5 lines) in packages/muya/test/spec/runner.ts:3
  • info Commented-code block (5 lines) in packages/muya/examples/src/data.ts:1
  • info Commented-code block (12 lines) in packages/muya/src/__tests__/getTOC.spec.ts:11
  • info Commented-code block (6 lines) in packages/muya/src/state/getTOC.ts:18
  • info Commented-code block (10 lines) in packages/muya/src/state/index.ts:156
  • info Commented-code block (5 lines) in packages/muya/src/state/renderToStaticHTML.ts…
View all commented-out code findings →
Config drift 25 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
12 matching findings on this repo
  • high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c…
  • low File has no detected symbols: eslint.config.js
  • low File has no detected symbols: packages/muya/vite.config.ts
  • low File has no detected symbols: packages/muya/vitest.spec.config.ts
  • low File has no detected symbols: packages/muya/src/config/emptyStates.ts
  • low File has no detected symbols: packages/muya/src/config/escapeCharacter.ts
  • low File has no detected symbols: packages/muya/src/config/emojis.ts
  • low File has no detected symbols: packages/muya/src/ui/linkTools/config.ts
  • low File has no detected symbols: packages/muya/src/ui/imageToolbar/config.ts
  • low File has no detected symbols: packages/muya/src/ui/inlineFormatToolbar/config.ts
  • low File has no detected symbols: packages/muya/src/ui/inlineFormatToolbar/__tests_…
  • low File has no detected symbols: packages/muya/src/ui/tableColumnToolbar/config.ts
View all config drift findings →
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/4c1de7b2-365c-44c3-80e5-6a709205365d/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/4c1de7b2-365c-44c3-80e5-6a709205365d/

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.