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

Scan timing: clone 4.84s · analysis 28.49s · 37.8 MB · GitHub API rate-limit (preflight)

spring-projects/spring-boot

https://github.com/spring-projects/spring-boot · scanned 2026-06-05 07:23 UTC (5 days, 23 hours ago) · 10 languages

234 raw signals (100 security + 134 graph) 11/13 scanners ran 45th percentile · Java · huge (>500K LoC) System graph score 63 (higher by 14)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 23 hours ago · v2 · 85 actionable findings from 2 signal sources. 82 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 40.0 0.15 6.00
security_score 100.0 0.25 25.00
testing_score 80.0 0.20 16.00
documentation_score 68.0 0.15 10.20
practices_score 81.0 0.15 12.15
code_quality 80.0 0.10 8.00
Overall 1.00 77.3
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 1 finding
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/`.
1 matching finding on this repo
  • info Commented-code block (6 lines) in smoke-test/spring-boot-smoke-test-web-groovy-…
View all commented-out code findings →
Config drift 11 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.
11 matching findings on this repo
  • critical Possible secret in module/spring-boot-artemis/src/main/java/org/springframework… module/spring-boot-artemis/src/main/java/org/spri…:67
  • low Very large file: module/spring-boot-hibernate/src/test/java/org/springframework…
  • low Very large file: module/spring-boot-kafka/src/test/java/org/springframework/boo…
  • low Very large file: module/spring-boot-opentelemetry/src/test/java/org/springframe…
  • low Very large file: module/spring-boot-flyway/src/test/java/org/springframework/bo…
  • low Very large file: module/spring-boot-webflux/src/test/java/org/springframework/b…
  • low Very large file: module/spring-boot-amqp/src/test/java/org/springframework/boot…
  • low Very large file: module/spring-boot-pulsar/src/test/java/org/springframework/bo…
  • low Very large file: module/spring-boot-webmvc/src/test/java/org/springframework/bo…
  • low Very large file: core/spring-boot/src/test/java/org/springframework/boot/contex…
  • low Very large file: core/spring-boot/src/test/java/org/springframework/boot/contex…
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/90eb9932-2940-47c9-aed3-67b7a21c25b6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/90eb9932-2940-47c9-aed3-67b7a21c25b6/

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.