yugabyte/yugabyte-db

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.

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

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 427.06s for a 833.3 MB repo slow.
Repobility's analysis ran in 75.7s after the clone landed.

https://github.com/yugabyte/yugabyte-db · scanned 2026-06-05 22:30 UTC (1 week, 2 days ago) · 10 languages

487 findings 11/13 scanners ran 55th percentile · Java · huge (>500K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

149 actionable findings from 1 signal source. 338 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	65.0	0.15	9.75
`security_score`	100.0	0.25	25.00
`testing_score`	81.0	0.20	16.20
`documentation_score`	68.0	0.15	10.20
`practices_score`	83.0	0.15	12.45
`code_quality`	51.0	0.10	5.10
Overall		1.00	78.7

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 6 High 41 Medium 22 Low 18 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 149 System graph 0 Crowd 0 Layer: Software 16 Quality 86 Security 10 Cicd 37

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 [MINED131] pre-commit hook `https://github.com/pre-commit/pre-commit-hooks` pin… src/postgres/third-party-extensions/postgresql_an…:3
high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… managed/node-agent/ynp/yba/request.go:45

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/1ef6c72a-4ac4-42c5-8abb-dfdbe54f196e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1ef6c72a-4ac4-42c5-8abb-dfdbe54f196e/

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.