Spring HATEOAS - Library to support implementing representations for hyper-text driven REST web services.
1.1k
Stars
469
Forks
288
Open issues
30
Contributors
AI Analysis
Spring HATEOAS is a library that simplifies the creation of HATEOAS (Hypermedia As The Engine Of Application State) REST representations in Spring applications, focusing specifically on link creation and representation assembly. It is designed for Java developers building REST APIs that need to follow hypermedia-driven design principles, particularly those working with Spring MVC. This is a specialized tool for a technical niche: REST API developers who require HATEOAS compliance, not a gener...
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Spring HATEOAS: a 14-year-old library for building REST APIs that follow hypermedia-driven design principles
Spring HATEOAS is a Spring Framework library designed to simplify the construction of REST representations that follow the HATEOAS (Hypermedia As The Engine Of Application State) principle. It abstracts link creation and representation assembly for REST APIs. Used primarily by Spring developers building REST services that require hypermedia controls. Matters because hypermedia-driven REST is a formal architectural style, though adoption of true HATEOAS in production remains niche compared to document-based REST APIs.
Created in 2012 during the early wave of REST API adoption and HATEOAS specification discussions. Part of the broader Spring ecosystem. Has evolved through multiple major versions and remains under active Spring project governance with multiple supported branches (1.0.x through current main).
Growth has been gradual and flat over time. 1,086 stars accumulated over 14 years suggests stable but limited adoption rather than explosive growth. No stars gained in last 7 days suggests momentum is not accelerating. Project maintains multiple version branches (0.25.x, 1.0.x, 1.1.x, 1.2.x, main) indicating long-term support model rather than rapid innovation cycle.
Adoption not verified. README provides no case studies, adoption metrics, or corporate user mentions. Being part of the official Spring Projects organization carries implicit credibility but does not confirm production usage scale. Presence of multiple maintained version branches suggests existing installed base, but size and scope cannot be quantified from available metadata.
Based on README, Spring HATEOAS provides APIs for link creation and representation assembly. Likely operates as middleware/utility layer atop Spring MVC for building hypermedia-aware responses. README does not detail implementation patterns, so architectural decisions remain opaque.
Not documented in README excerpt provided.
Last push 2026-06-09 (26 days before analysis date) indicates active maintenance. Multiple CI pipelines visible in README (main, 1.2.x, 1.1.x, 1.0.x, 0.25.x branches all tracked) suggest disciplined long-term support. Maintenance is steady rather than intensive; consistent with a mature utility library in a stable category rather than rapid development.
ADOPT IF: building Spring-based REST APIs where hypermedia-driven resource navigation is a core architectural requirement, and your team has clarity on HATEOAS design patterns. AVOID IF: building simple CRUD REST APIs, or if your API clients expect JSON-first document APIs without embedded links; HATEOAS adds abstraction overhead in these scenarios. MONITOR IF: considering adoption of hypermedia-driven APIs as an organization; the modest ecosystem adoption suggests HATEOAS remains a niche practice, though Spring HATEOAS is the appropriate tool if you commit to that path.
Independent dimensions
Mainstream potential
3/10
Technical importance
6/10
Adoption evidence
4/10
- Limited ecosystem adoption may signal that HATEOAS design patterns themselves have limited market demand despite theoretical merit; adoption of the library could reflect adoption of the architectural style rather than library-specific quality.
- Multiple long-term version branches (0.25.x through main) require active maintenance effort; if Spring project resourcing changes, older branches may be neglected.
- HATEOAS clients (browsers, API consumers) must understand hypermedia semantics; tooling and framework support for consuming HATEOAS APIs is fragmented compared to document-based REST, creating integration friction.
- No adoption metrics in README or visible marketing suggest the Spring team does not actively measure or publicize real-world usage; unclear if user base is growing, stable, or declining.
- Flat star growth over 14 years may indicate the project has reached a stable ceiling in applicable use cases rather than remaining growth potential.
Spring HATEOAS will likely remain a stable, well-maintained utility library for the subset of Spring developers committed to hypermedia-driven REST design. Expect continued slow growth, not rapid adoption. Most likely to see increases in usage if REST API architectural standards evolve to favor hypermedia (low probability), or within specific domains (financial services, enterprise systems) that already value link-driven navigation.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Java
- License
- Apache-2.0
- Last updated
- 1mo ago
- Created
- 173mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Downgrade to Kotlin 2.3.21 and Kotlin Coroutines 1.10.2
@Size on String properties renders as HAL-FORMS type: "range" with min/max instead of a text input with minLength/maxLength
Using Java Records as Hal Form Request Body Types
Prevent accidental non-anonymous use of `TypeReferences`
In some situations, `HateoasConfiguration#lookupMessageSource` wrongly returns null instead of `ReloadableResourceBundleMessageSource`
Top contributors
Recent releases
Similar repos
willdurand/Hateoas
Hateoas is a PHP library for building REST web services that implement HATEOAS...
odrotbohm/spring-restbucks
Spring Restbucks is a reference implementation of the Restbucks application...
springdoc/springdoc-openapi
springdoc-openapi is a Spring Boot library that automatically generates OpenAPI...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
spring-projects/spring-hateoas
this
|
1.1k | +2 | Java | 7/10 | 1mo ago |
|
willdurand/Hateoas
|
1k | — | PHP | 7/10 | 6mo ago |
|
odrotbohm/spring-restbucks
|
1.3k | — | Java | 7/10 | 3mo ago |
|
springdoc/springdoc-openapi
|
3.7k | — | Java | 8/10 | 3w ago |
|
spring-projects/spring-restdocs
|
1.2k | — | Java | 8/10 | 4w ago |
3.4× higher star count. Addresses OpenAPI/Swagger generation rather than HATEOAS; solves a different problem (API documentation and contract-first development) that has seen broader industry adoption than hypermedia-driven REST.
Similar star count (1,180 vs 1,086). Focused on REST API documentation and testing. Addresses parallel concern (documentation) rather than direct competition; projects are often used together.
Near parity in stars (1,040 vs 1,086) despite different language ecosystem. Suggests HATEOAS adoption is consistently modest across ecosystems, not a Java-specific phenomenon.
Higher star count (1,319). Reference implementation/tutorial for REST best practices with Spring, not a direct tool competitor; demonstrates patterns rather than providing reusable library.
