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.

medusajs/medusa

https://github.com/medusajs/medusa.git · scanned 2026-05-17 19:53 UTC (2 weeks, 4 days ago) · 10 languages

3637 findings (59 legacy + 3578 scanner) 8/10 scanners ran 31st percentile · Typescript · huge (>500K LoC) Scanner says 55 (higher by 24)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 4 days ago · v2 · 59 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Severity distribution — click a segment to filter
Active filters: layer: data × excluding tests × Reset all
Scan summary Repository scanned at 54.9/100 with 100.0% coverage. It contains 28124 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 0 findings. Risk profile is low: 0 critical, 0 high, 0 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 0 of 59 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

No findings match the active filters. Reset →
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/5f88f9b1-bad0-4cff-861c-da0f06324fff/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5f88f9b1-bad0-4cff-861c-da0f06324fff/

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.