Spring Upgrade Radar
Local-first Spring Boot 3 migration scanner

Spring Boot 3 migration estimates in minutes, not meetings.

Scan a Spring Boot 2.x project locally and generate an executive summary, risk score, estimated roadmap, and migration tickets before committing your team to the upgrade.

Generate a free migration report View sample report
quick-start.sh 
$ git clone https://github.com/purewater02/spring-upgrade-radar.git
$ cd spring-upgrade-radar && pip install -e .
$ spring-upgrade-radar scan /path/to/spring-project \
    --target 3.5 \
    --output out/report.md \
    --html-output out/report.html \
    --tickets-json out/tickets.json
Why it exists

Spring Boot 3 upgrades hide multiple migrations in one release.

Java 17, Jakarta namespaces, Spring Security 6, Hibernate 6, and dependency compatibility can land at the same time. The first question is not “can we upgrade?” — it is “what will break, and how many sprints should we reserve?”

Detect upgrade risks

Find Java baseline gaps, javax.persistence imports, legacy Spring Security configuration, JSP/JSTL risks, and dependency coordinate issues.

Score readiness

Get a risk score and readiness grade that makes migration complexity easy to explain to tech leads, EMs, CTOs, and PMs.

Export tickets

Generate Markdown, HTML, JSON, Jira CSV, and GitHub Issues Markdown so findings become actionable engineering work.

Sample output

From source scan to sprint plan.

A generated report combines stakeholder-friendly summary with developer-ready evidence and tickets.

Executive Summary Risk score 100/100 · Grade C
4sprint roadmap
1. Spring Boot 2.x → 3.x major migration
2. Java 17 baseline gap
3. JPA javax.persistence imports
01

Java 17+ baseline

Update JDK/toolchain and make CI green.

02

Jakarta migration

Replace javax imports and validate JPA/servlet compatibility.

03

Dependency upgrades

Resolve Security, Hibernate, OpenAPI, and driver changes.

04

Boot 3 validation

Run full tests, smoke tests, and runtime verification.

Privacy

Built for teams that cannot upload source code.

Spring Upgrade Radar is local-first. Run it in your own repository, CI, or private runner. The default workflow generates reports without uploading source code to a hosted service.

CLI-first adoption

Start with a free local report. Add the composite GitHub Action when you want repeatable CI checks and artifacts.

Report-first monetization

Every report can become a Pro assessment: PDF, dependency matrix, richer sprint plan, and team workflow exports.

Packaging

Start free. Upgrade when the report becomes a team plan.

Initial pricing is intentionally simple while demand is validated. The GitHub Action is free; paid Pro services are optional external add-ons, not paid Marketplace plans.

Free CLI + GitHub Action

$0
Local Markdown/HTML report in CLI or CI
  • risk score
  • core findings
  • Jira/GitHub ticket exports

Pro Report

$49
Optional external review per repo
  • reviewed report
  • dependency risk notes
  • prioritized sprint roadmap

Team Assessment

From $299
For multi-module or critical services
  • multi-repo review
  • CI rollout guidance
  • custom rules
Next step

Know your Spring Boot 3 migration risk before the upgrade starts.

Generate a report, share the roadmap, and turn the findings into migration tickets.

Generate a free migration report Read the migration checklist