spring-projects/spring-data-jpa

Simplifies the development of creating a JPA-based data access layer.

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 21st, 2026
Created on November 11th, 2010
Open Issues & Pull Requests: 124 (+0)
GitHub issues: Enabled
Number of forks: 1,574
Total Stargazers: 3,285 (+0)
Total Subscribers: 190 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.8 hours
Mean response time: 32.9 days
90th percentile: 28.1 days
Tracked items: 658

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 73% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "status: waiting-for-triage" is answered fastest, typically in about 4 hours, while "type: task" waits about 4 weeks. 89% of issues opened in the past year have been closed, leaving a working backlog. Three people close 91% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 49
New in 7 days: 3
Closed in 7 days: 5
Avg open age: 851 days
Stale 30+ days: 39
Stale 90+ days: 27

Recent activity

Opened in 7 days: 3
Closed in 7 days: 5
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • type: dependency-upgrade (119)
  • type: task (103)
  • type: enhancement (93)
  • for: external-project (69)
  • type: bug (69)
  • status: duplicate (36)
  • status: waiting-for-triage (34)
  • type: regression (33)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Spring Data JPA is a framework that simplifies the development of JPA-based data access layers.

The problem it solves is the boilerplate code burden traditionally required to implement data access layers—writing repetitive code for simple queries, pagination, and auditing. Spring Data JPA reduces this effort by allowing developers to define repository interfaces with custom finder methods, and the framework automatically provides the implementation. Query methods are generated dynamically from method names, and JPA NamedQueries are triggered transparently. The framework also handles CRUD operations, domain base classes with basic properties, and transparent auditing of created and last-changed timestamps.

Developers should choose this tool when building Spring-powered applications that use JPA for data access and want to minimize boilerplate. It suits projects of any scale that benefit from reduced implementation effort for data access layers. The framework integrates seamlessly with Spring configuration and allows custom repository code to be integrated where needed.

The project maintains active development with regular updates to its codebase. It demonstrates consistent engagement with the Spring ecosystem through integration with Spring's broader infrastructure and tooling. The project is governed by the Spring Code of Conduct and maintains community standards for participation.