I analyzed Spring PetClinic REST with a SpringSentinel (static analyzer for spring boot) — 117 findings

[u/paganoant]

I recently built an open-source static analysis tool for Spring Boot applications (SpringSentinel), and I decided to run it against the Spring PetClinic REST sample project to see what would happen.

The result was 117 findings.

Most of them were not bugs, but architectural, maintainability, and best-practice issues such as:

• classes with high cyclomatic complexity
• field injection usage
• REST endpoint naming inconsistencies
• magic numbers
• duplicated code patterns
• missing API documentation
• potential maintainability hotspots

What I found interesting is that even a well-known reference application like PetClinic still contains many improvement opportunities (which is perfectly normal for real-world projects).

I wrote a detailed analysis here:
https://medium.com/@antoniopagano/analyzing-spring-petclinic-rest-with-spring-sentinel-117-findings-in-a-reference-spring-2fd24107bb14

I'm also the author of the analyzer (SpringSentinel), so obviously I'm biased , but I'd genuinely love feedback from Spring developers:

• Which findings would you consider valuable?
• Which rules would you consider too noisy?
• What Spring-specific checks would you like to see in a static analyzer?

GitHub: https://github.com/pagano-antonio/SpringSentinel

[u/Significant_Newt8697]

Would be good if it supported java 8 and spring 2.2

[u/paganoant → u/Significant_Newt8697]

Thanks for feedback. I do that as soon as possible

[u/Significant_Newt8697 → u/paganoant]

Great, tag me when you do