spring-projects/spring-petclinic

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.

https://github.com/spring-projects/spring-petclinic.git · scanned 2026-05-16 11:56 UTC (1 day, 9 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, 10 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

{# ── 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: medium × excluding tests × Reset all

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 7 of 22 findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium Legacy security auth conf 0.92 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks but does not define .repobility/access.yml or equivalent authorization documentation.

The repository uses web/API frameworks but does not define .repobility/access.yml or equivalent authorization documentation.

authlegacy

medium Legacy cicd docker conf 0.88 Database service has no healthcheck

Compose starts dependent containers in dependency order, but it does not wait for a database to be ready unless a healthcheck is defined and dependents use service_healthy.

docker-compose.yml:13 dockerlegacy

medium Legacy cicd docker conf 0.88 Database service has no healthcheck

Compose starts dependent containers in dependency order, but it does not wait for a database to be ready unless a healthcheck is defined and dependents use service_healthy.

docker-compose.yml:1 dockerlegacy

medium Legacy cicd docker conf 0.90 Docker build context has no .dockerignore

Without .dockerignore, build context can include source history, local env files, dependencies, and generated artifacts.

.dockerignore dockerlegacy

medium Legacy cicd docker conf 0.82 Docker final stage has no non-root USER

Docker images run as root unless the image or Dockerfile switches to a non-root user.

.devcontainer/Dockerfile:3 dockerlegacy

medium 9-layer cicd supply-chain conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned

gradle/actions/setup-gradle@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

.github/workflows/gradle-build.yml:29 supply-chaingithub-actionspinned-dependencies

medium 9-layer security coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). Either auth lives in custom code, in a separate service, or is missing.

coverageauth

{# ── 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.