doctrine/persistence

The Doctrine Persistence project is a library that provides common abstractions for object mapper persistence.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 15 minutes ago
Added to GitGenius on September 17th, 2026
Created on June 6th, 2018
Open Issues & Pull Requests: 13 (+0)
GitHub issues: Enabled
Number of forks: 77
Total Stargazers: 4,045 (+0)
Total Subscribers: 20 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.0 hours
Mean response time: 273.7 days
90th percentile: 1532.1 days
Tracked items: 12

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 681 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • BC Break (1)
  • Bug (1)
  • Good First Issue (1)
  • Improvement (1)

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

Doctrine Persistence is a library that provides common abstractions for object mapper persistence.

The library solves the problem of inconsistency across different object mapping implementations by establishing a shared interface layer. Rather than requiring developers to learn and adapt to the specific APIs of individual persistence tools, Doctrine Persistence defines a set of common contracts and abstractions that object mappers can implement. This approach allows code written against the Doctrine Persistence interfaces to work with multiple underlying persistence implementations without modification.

Developers should choose this library when building tools, frameworks, or applications that need to support multiple object mapping solutions or when creating libraries that should remain agnostic to the specific persistence implementation their users employ. It suits projects where flexibility across different persistence layers is valuable, such as framework integrations, plugin systems, or multi-database applications. The library is particularly useful for maintainers of packages that depend on object mapping functionality but want to avoid coupling to a single persistence solution.

The project maintains a steady stream of contributions and demonstrates active engagement with the community through issue resolution and pull request reviews. Development activity shows consistent attention to code quality and compatibility across different PHP versions and object mapper implementations. The project receives regular updates to address compatibility concerns and to refine the abstraction layer based on real-world usage patterns.