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

supabase/supabase

https://github.com/supabase/supabase · scanned 2026-06-05 06:03 UTC (3 hours, 56 minutes ago) · 10 languages

43 findings 11/13 scanners ran 26th percentile · Typescript · medium (20-100K LoC)

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

Complete repo analysis

43 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

Combined
73.5
/100
Repobility
74
43 legacy
9-layer
—
—% cov · 0 gaps
Critical
11
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 0.0 0.20 0.00
documentation_score 60.0 0.15 9.00
practices_score 63.0 0.15 9.45
code_quality 80.0 0.10 8.00
Overall 1.00 60.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 11 High 16 Medium 4 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 43 9-layer 0 Crowd 0 Layer: Security 2 Quality 30 Software 11

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.

Fragile runtime 28 findings
What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.
Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.
How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.
Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).
12 matching findings on this repo
  • medium React interval is created without an explicit cleanup apps/design-system/registry/default/example/page-…:293
  • medium [SEC087] JS: weak Math.random for crypto: Math.random() is not cryptographicall… apps/design-system/registry/default/example/logs-…:14
  • low Duplicated implementation block across source files apps/design-system/registry/default/block/chart-c…:37
  • low Duplicated implementation block across source files apps/design-system/registry/default/block/chart-c…:35
  • low Duplicated implementation block across source files apps/design-system/registry/default/block/chart-c…:1
  • low Duplicated implementation block across source files apps/design-system/registry/default/block/chart-c…:1
  • low Duplicated implementation block across source files apps/design-system/registry/default/block/chart-c…:1
  • low Duplicated implementation block across source files apps/design-system/registry/default/block/chart-c…:46
  • low Duplicated implementation block across source files apps/design-system/registry/default/block/chart-c…:1
  • low Duplicated implementation block across source files apps/design-system/registry/default/block/chart-c…:3
  • low Duplicated implementation block across source files apps/design-system/registry/default/block/chart-c…:1
  • low Duplicated implementation block across source files apps/design-system/registry/default/block/chart-c…:1
View all fragile runtime 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/d934b2dd-fd64-4869-b7de-e0c046282e0b/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d934b2dd-fd64-4869-b7de-e0c046282e0b/

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.