mermaid-js/mermaid

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.

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

Scan timing: clone 9.59s · analysis 69.97s · 14.4 MB · GitHub API rate-limit (preflight)

https://github.com/mermaid-js/mermaid · scanned 2026-06-05 07:02 UTC (6 days ago) · 10 languages

666 raw signals (188 security + 478 graph) 9th percentile · Typescript · large (100-500K LoC) System graph score 81 (lower by 20)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 231 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	12.7	0.25	3.17
`testing_score`	77.0	0.20	15.40
`documentation_score`	86.7	0.15	13.01
`practices_score`	100.0	0.15	15.00
`code_quality`	58.3	0.10	5.83
Overall		1.00	61.4

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 44 Medium 51 Low 122 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 135 System graph 231 Crowd 0 Layer: Quality 94 Security 10 Software 139 Cicd 9 Api 1 Frontend 110 Network 2 Hardware 1

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.

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `staleOrLegacy` in packages/mermaid/src/rendering-u…

View all legacy markers findings →

Commented-out code 50 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 (9 lines) in eslint.config.js:172
info Commented-code block (5 lines) in packages/mermaid-layout-tidy-tree/src/render.…
info Commented-code block (5 lines) in packages/mermaid/src/diagrams/venn/vennRender…
info Commented-code block (13 lines) in packages/mermaid/src/diagrams/er/erRenderer.…
info Commented-code block (7 lines) in packages/mermaid/src/diagrams/state/stateDiag…
info Commented-code block (7 lines) in packages/mermaid/src/diagrams/state/stateDiag…
info Commented-code block (7 lines) in packages/mermaid/src/diagrams/state/shapes.js…
info Commented-code block (6 lines) in packages/mermaid/src/diagrams/architecture/ar…
info Commented-code block (5 lines) in packages/mermaid/src/diagrams/gantt/ganttDb.j…
info Commented-code block (7 lines) in packages/mermaid/src/diagrams/swimlanes/swiml…
info Commented-code block (10 lines) in packages/mermaid/src/dagre-wrapper/edges.js:…
info Commented-code block (6 lines) in packages/mermaid/src/diagram-api/regexes.ts:1

View all commented-out code findings →

Config drift 12 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… packages/mermaid-local-editor/static/js/renderer.…:22
low File has no detected symbols: vite.config.ts
low File has no detected symbols: cypress.config.ts
low File has no detected symbols: eslint.config.js
low File has no detected symbols: tests/webpack/webpack.config.js
low File has no detected symbols: packages/mermaid/src/config.spec.ts
info TODO/FIXME marker in shipping code — vite.config.ts:18
info TODO/FIXME marker in shipping code — eslint.config.js:172
info TODO/FIXME marker in shipping code — packages/mermaid/src/defaultConfig.ts:21
info TODO/FIXME marker in shipping code — packages/mermaid/src/docs/vite.config.ts:56
low Very large file: packages/mermaid/src/config.type.ts (2070 lines)
info Commented-code block (9 lines) in eslint.config.js:172

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/eb0e01a6-f8a4-4dcb-b77b-71f719fa226f/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/eb0e01a6-f8a4-4dcb-b77b-71f719fa226f/

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.