somesanity/draw-io-obsidian

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.

12 of your 31 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

https://github.com/somesanity/draw-io-obsidian · scanned 2026-06-05 19:32 UTC (4 days, 16 hours ago) · 10 languages

51 raw signals (29 security + 22 graph) 11/13 scanners ran 43rd percentile · Typescript · small (2-20K LoC) System graph score 96 (lower by 31)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 10 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	100.0	0.25	25.00
`testing_score`	0.0	0.20	0.00
`documentation_score`	60.0	0.15	9.00
`practices_score`	57.0	0.15	8.55
`code_quality`	80.0	0.10	8.00
Overall		1.00	65.5

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 0 High 0 Medium 6 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 22 System graph 10 Crowd 0 Layer: Quality 14 Security 5 Cicd 1 Software 8 Api 1 Frontend 3

Exclude dismissed / FP Exclude test files

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.

Config drift 2 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.

2 matching findings on this repo

high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… src/Utils/MxGraphParser.ts:5
high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… src/MarkdownPostProcessors/interactiveDiagrams.ts:34

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/9b2af68d-cca1-4f80-80b5-25c93f56bb98/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9b2af68d-cca1-4f80-80b5-25c93f56bb98/

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.