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

spring-projects/spring-petclinic

https://github.com/spring-projects/spring-petclinic.git · scanned 2026-05-16 11:56 UTC (1 day, 8 hours ago) · 10 languages

41 findings (14 legacy + 27 scanner) Scanner says 89 (lower by 10)

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

Complete repo analysis

Last scanned 1 day, 9 hours ago · v3 · 22 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
86.8
/100
Repobility
84
13 legacy
9-layer
89
88.9% cov · 9 gaps
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
{# ── 2026-05-17 R27 #5: score breakdown panel ────────────────────── Surfaces the score_breakdown JSON that's been silently stored on Repository for months. Turns hidden math into a trust signal. #}
Severity distribution — click a segment to filter
Active filters: severity: high × excluding tests × Reset all
Severity: Critical 2 High 4 Medium 8 Low 6 Source: Legacy 13 9-layer 9 Crowd 0 Layer: Security 3 Cicd 16 Api 1 Hardware 1 Frontend 1
Scan summary Repository scanned at 89.2/100 with 88.9% coverage. It contains 151 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 9 findings — concentrated in cicd (5), api (1), hardware (1). Risk profile is low: 0 critical, 0 high, 3 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

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

high Legacy cicd docker conf 0.90 Database service has no persistent data volume
Database containers store data in the writable container layer unless a volume or bind mount is attached to the image's data directory. Recreating the container can lose state.
docker-compose.yml:13 dockerlegacy
high Legacy cicd docker conf 0.90 Database service has no persistent data volume
Database containers store data in the writable container layer unless a volume or bind mount is attached to the image's data directory. Recreating the container can lose state.
docker-compose.yml:1 dockerlegacy
high Legacy cicd docker conf 0.84 Database service publishes a host port
Publishing database ports to the host increases exposure. Internal Compose networking usually only needs expose, not ports.
docker-compose.yml:13 dockerlegacy
high Legacy cicd docker conf 0.84 Database service publishes a host port
Publishing database ports to the host increases exposure. Internal Compose networking usually only needs expose, not ports.
docker-compose.yml:1 dockerlegacy
{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/c178890f-6675-47fe-8e92-afc336f12807/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c178890f-6675-47fe-8e92-afc336f12807/

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.