Doctrine2 ORM Data Fixtures Extensions
2.9k
Stars
231
Forks
38
Open issues
30
Contributors
AI Analysis
Doctrine Data Fixtures Extension provides a PHP library for managing and executing data fixtures with the Doctrine ORM and ODM. It is a specialized tool built specifically for developers working with Doctrine-based projects who need to seed databases with test or initial data. General-purpose PHP developers or those using other ORMs will not benefit from this project.
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.
Doctrine Data Fixtures: stable, maintenance-mode library for ORM/ODM test data setup in PHP
doctrine/data-fixtures is a fixture loading library for Doctrine ORM and ODM, enabling developers to populate test databases with seed data. Built as an extension to Doctrine core libraries starting in 2010, it serves PHP developers who need reproducible test environments. Adoption appears concentrated within the Doctrine ecosystem and PHP testing communities; the project shows steady maintenance rather than active growth, suggesting it has reached a stable, mature state where the core problem is solved.
Created in 2010 alongside Doctrine 2's rise, data-fixtures emerged as the de facto solution for managing test data in Doctrine-based applications. It has evolved incrementally to support multiple Doctrine versions and ODM implementations, with development patterns reflecting a consolidated, well-established problem domain rather than active innovation.
The project gained stars steadily through the 2010s as Doctrine became the dominant ORM in PHP. Growth appears to have plateaued around 2,850 stars, indicating market saturation rather than decline. Recent activity (zero stars gained in 7 days, last push on 2026-07-08) suggests the project is in maintenance equilibrium—addressing bugs and compatibility needs without seeking to expand its scope. The flat growth trajectory is consistent with a solved, stable category rather than abandonment.
Adoption not directly verified from repository metadata alone. However, strong contextual evidence suggests real-world use: (1) 2,850 stars indicates established mindshare; (2) inclusion in official Doctrine project portfolio; (3) presence of related bundle (DoctrineFixturesBundle, 2,530 stars) suggests integration into framework ecosystems; (4) documented CI/CD and maintained status imply production-grade expectations from maintainers. Widespread adoption is likely within Symfony and pure Doctrine shops, but precise production usage scale is not quantifiable from metadata.
Based on README, the library provides a fixture loading framework for Doctrine ORM/ODM with test execution capabilities. Likely follows a loader/executor pattern to manage fixture dependencies and database persistence. The presence of phpunit in dev requirements suggests integrated testing patterns, though README does not detail architectural layers, dependency injection patterns, or extension points.
Not documented in README. README mentions phpunit is included in dev requirements and provides test execution instructions, but does not report coverage metrics, test count, or coverage targets.
Last push dated 2026-07-08 (current date), confirming active maintenance. Project carries official Doctrine license (MIT) and workflows (build status badge indicates CI/CD in place). Absence of visible urgency in recent commits and zero 7-day star growth aligns with steady-state maintenance rather than reactive firefighting or rapid iteration.
ADOPT IF: you are using Doctrine ORM/ODM in PHP and need reproducible, managed test fixtures; you benefit from declarative fixture definitions and dependency ordering; you are integrating with Symfony (via DoctrineFixturesBundle) or native Doctrine setups. AVOID IF: you prefer programmatic factory-based test data generation; you use non-Doctrine ORMs or document databases without Doctrine mapping; you need advanced data transformation or generation logic beyond simple persistence. MONITOR IF: your project is evaluating long-term Doctrine commitment; you are considering shifting to factory-based testing patterns; you need support for Doctrine versions beyond those tested in current CI pipeline.
Independent dimensions
Mainstream potential
3/10
Technical importance
6/10
Adoption evidence
6/10
- Maintenance mode status means feature requests and architectural improvements may move slowly or be declined in favor of stability. New test paradigms (factories, behavior-driven scenarios) may not receive first-class support.
- Tightly coupled to Doctrine versioning; breaking changes in Doctrine ORM/ODM could require coordinated updates. README does not specify minimum/maximum supported Doctrine versions, creating potential compatibility gaps.
- Adoption appears concentrated within Doctrine ecosystem; limited visibility in broader PHP testing or CI/CD communities suggests knowledge transfer and adoption ramp-up may be higher for teams without Doctrine experience.
- No evidence of active documentation evolution; README truncation and lack of versioned changelog visibility in metadata means consumers may struggle to identify which features are current vs. deprecated.
- Zero recent star growth and flat trajectory suggest the project may not attract new maintainers or contributors; bus factor risk if core maintainers shift focus.
doctrine/data-fixtures will likely remain a stable, narrowly-scoped library serving the Doctrine + Symfony testing ecosystem indefinitely. Expect slow, reactive maintenance rather than new features. Gradual erosion possible if factory-based testing (e.g., Nelmio Alice, FactoryBot-style patterns) achieves wider PHP adoption, but core use case (bulk seed data for integration tests, CI/CD) is unlikely to disappear entirely. Project trajectory suggests permanent niche rather than growth or sunset.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- http://www.doctrine-project.org
- Language
- PHP
- License
- MIT
- Last updated
- 3d ago
- Created
- 192mo 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
`Class "Doctrine\Bundle\FixturesBundle\Fixture" not found in prod env
MongoDBPurger doesn't purge chunks collection
Support class inheritance in `getReference` and related methods
Using numerics any reference name causes error with v1.8.1
Persistent ReferenceRepository to be used in tests
Top contributors
Recent releases
Similar repos
doctrine/DoctrineFixturesBundle
DoctrineFixturesBundle integrates Doctrine Data Fixtures into Symfony...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
doctrine/data-fixtures
this
|
2.9k | — | PHP | 7/10 | 3d ago |
|
doctrine/DoctrineFixturesBundle
|
2.5k | — | PHP | 8/10 | 3d ago |
|
doctrine/orm
|
10.2k | — | PHP | 8/10 | 7h ago |
|
doctrine/persistence
|
4k | — | PHP | 8/10 | 3w ago |
|
doctrine/migrations
|
4.8k | — | PHP | 8/10 | 3w ago |
 dmaicher/doctrine-test-bundle
|
1.2k | — | PHP | 8/10 | 1mo ago |
Sibling project (2,530 stars) providing Symfony integration layer on top of data-fixtures. Complementary rather than competing; DoctrineFixturesBundle wraps data-fixtures for Symfony developers, while data-fixtures remains the lower-level library.
Faker generates synthetic test data; data-fixtures manages loading and persistence. Often used together—data-fixtures handles the 'where' and 'when' of fixture execution, Faker handles the 'what' of data generation.
Alice provides higher-level fixture definition syntax. If active, represents an alternative DSL layer that could sit atop or replace data-fixtures' approach, though no direct evidence of this in provided metadata.
data-fixtures abstracts ORM-based fixture loading; teams using raw SQL migrations for test setup avoid this library entirely, accepting higher maintenance burden for maximum control.
Modern testing practices increasingly favor factory builders over fixture files. data-fixtures remains relevant for bulk seed data and CI/CD scenarios but may face gradual adoption pressure from factory-based approaches.
