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

Scan timing: clone 22.3s · analysis 27.5s · 42.1 MB · GitHub API rate-limit (preflight)

Apicurio/apicurio-registry

https://github.com/Apicurio/apicurio-registry · scanned 2026-06-05 13:09 UTC (5 days, 9 hours ago) · 10 languages

1045 raw signals (429 security + 616 graph) 11/13 scanners ran 100th percentile · Java · large (100-500K LoC) System graph score 73 (higher by 12)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 80.0 0.20 16.00
documentation_score 88.0 0.15 13.20
practices_score 73.0 0.15 10.95
code_quality 78.0 0.10 7.80
Overall 1.00 85.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

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.

Commented-out code 3 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/`.
3 matching findings on this repo
  • info Commented-code block (5 lines) in ui/tests/playwright.config.ts:51
  • info Commented-code block (8 lines) in ui/ui-app/src/editors/OpenApiEditor.tsx:35
  • info Commented-code block (9 lines) in ui/ui-app/src/app/pages/roles/components/moda…
View all commented-out code findings →
Config drift 9 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.
9 matching findings on this repo
  • high [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers c… ui/ui-app/src/utils/content.utils.ts:55
  • low File has no detected symbols: ui/tests/playwright.config.ts
  • low File has no detected symbols: ui/tests/eslint.config.js
  • low File has no detected symbols: ui/ui-docs/eslint.config.js
  • low File has no detected symbols: ui/ui-app/eslint.config.js
  • info TODO/FIXME marker in shipping code — ui/ui-editors/src/app/services/config.serv…
  • critical Possible secret in cli/src/main/java/io/apicurio/registry/cli/config/ConfigMode… cli/src/main/java/io/apicurio/registry/cli/config…:26
  • critical Possible secret in schema-resolver/src/main/java/io/apicurio/registry/resolver/… schema-resolver/src/main/java/io/apicurio/registr…:185
  • info Commented-code block (5 lines) in ui/tests/playwright.config.ts:51
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/c7ccf673-11a3-4b13-8cca-2624354a26fc/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c7ccf673-11a3-4b13-8cca-2624354a26fc/

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.