I'm Deendayal, and I built WireDoctor after one too many "why does this service suddenly take 40 seconds to boot?" debugging sessions. Spring Boot's Actuator gives you raw StartupStep JSON, but nobody ships the analysis layer on top of it so you're left manually digging through logs. WireDoctor fixes that. Add one dependency, and at startup it hooks into your real, resolved ApplicationContext and turns it into: 🔍 An interactive HTML report searchable dependency graph, real per-bean startup timings, no reflection heuristics 🚨 Cycle detection with fix advice Tarjan SCC finds silently-resolved bean cycles and ranks which @Lazy would break them 👻 Ghost bean detection finds beans that cost startup time/memory but show no sign of use (honestly labeled, never overclaimed) 🛡️ CI gates commit a baseline, and any PR that introduces a new cycle or startup-time regression fails the build automatically It's zero-intrusion (no dashboard server), runs fully offline, and works across Boot 2.7 through 4.0. You can try the exact sample report live, no install needed: https://ddsha441981.github.io/wi... Would love your feedback especially from anyone running large Spring Boot monoliths where startup time and hidden architectural debt are real pain points. Happy to answer any questions! 🙏

GitHub

Runtime diagnostics & CI gates for Spring Boot

Runtime diagnostics & CI gates for Spring Boot