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
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)

mermaid-js/mermaid

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
Combined
62.9
/100
Security checks
45
135 findings
System graph
81
100.0% cov · 231 findings
Critical
3
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 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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
pull_request_target workflow appears to check out untrusted PR code
GapSeverity.HIGH Layer.CICD score 0.375
Why: high severity
.github/workflows/validate-lockfile.yml
#2
Privileged port 256 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in Dockerfile is a real port, change the binding to ≥1024 or run behind a proxy.
Dockerfile
#3
Privileged port 40 in use
GapSeverity.MEDIUM Layer.NETWORK score 0.338
Why: medium severity · misconfigured network surface
Fix: If the number in Dockerfile is a real port, change the binding to ≥1024 or run behind a proxy.
Dockerfile
#4
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release-preview-publish.yml
#5
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/lint.yml
#6
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/publish-docs.yml
#7
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release-preview.yml
#8
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/scorecard.yml
#9
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml
#10
GitHub Actions workflow grants broad write permissions
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/e2e-timings.yml

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.