Symfony integration for the doctrine/data-fixtures library
2.5k
Stars
212
Forks
29
Open issues
30
Contributors
AI Analysis
DoctrineFixturesBundle integrates Doctrine Data Fixtures into Symfony applications, enabling programmatic loading of test data into the Doctrine ORM. It serves developers building Symfony applications who need to seed databases with fixture data for testing and development. This is a specialized integration tool for the Symfony/Doctrine ecosystem, not a general-purpose library.
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.
Stable Symfony integration layer for programmatic fixture loading via Doctrine ORM
DoctrineFixturesBundle bridges Symfony applications with doctrine/data-fixtures, enabling developers to load test and seed data into databases through PHP code rather than manual scripts. Built for Symfony projects that use Doctrine ORM, it remains the standard integration point for fixture management in that ecosystem. Adoption appears concentrated within the Symfony/Doctrine community; usage is implicit rather than publicly tracked.
Created in 2011 as Symfony-specific packaging for Doctrine's data fixtures functionality. Evolved alongside Symfony and Doctrine as a utility layer, not a replacement for those libraries. Maintains stable API to reduce friction for Symfony developers integrating fixtures into their workflow.
Initial growth (2011–2015) tracked Symfony adoption broadly. Star count plateaued around 2,500, suggesting adoption is mature and stable rather than expanding into new categories. No spike activity in recent years indicates the problem it solves is well-understood and stable, not emerging or trending.
Adoption not verified through direct metrics. Fixture loading is a standard need in Symfony/Doctrine projects, and this bundle is the canonical integration, implying widespread implicit use. However, no public case studies, adoption surveys, or enterprise deployments are documented in README.
Based on README, likely a thin integration layer that wraps doctrine/data-fixtures library and exposes it as a Symfony bundle (console commands, dependency injection). Specific implementation details not verifiable from provided metadata.
Not documented in README excerpt provided.
Last push 2026-07-08 (current date), indicating active monitoring. No star gains in last 7 days and stable fork count (212) suggest maintenance is reactive (bug fixes, compatibility updates) rather than feature-driven. Consistent with a mature, stable utility.
ADOPT IF: you are building a Symfony application with Doctrine ORM and need to load test data or seed databases programmatically; this is the standard, low-friction integration. AVOID IF: you are not using Symfony or Doctrine (use parent library directly), or if your fixture needs are non-standard (e.g., complex multi-database orchestration). MONITOR IF: you are evaluating whether fixture management belongs in your test suite vs. migrations—this bundle assumes fixtures are separate from schema migrations, which is a design choice worth validating against your workflow.
Independent dimensions
Mainstream potential
3/10
Technical importance
6/10
Adoption evidence
4/10
- Narrow scope means limited applicability outside Symfony/Doctrine ecosystem; not portable to other frameworks.
- Maintenance is reactive rather than feature-driven, which may delay adaptation to major Symfony version changes, though last push suggests active monitoring.
- No evidence of large-scale adoption or case studies; if widespread issues emerge, visibility and prioritization may lag.
- Dependency chain (Symfony + Doctrine + data-fixtures) creates potential version compatibility friction during major upgrades.
- Documentation is external (Symfony docs) rather than in README; onboarding friction for developers unfamiliar with Symfony bundle conventions.
Likely to remain a stable, low-velocity maintenance project. Will continue to track Symfony and Doctrine releases for compatibility but is unlikely to see significant feature expansion. Adoption will remain concentrated in Symfony/Doctrine shops and will not expand meaningfully into non-Symfony contexts.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- PHP
- License
- MIT
- Last updated
- 3d ago
- Created
- 185mo 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
bug: Fixtures are not loaded when autocommit mode is disabled
Question about default settings
In verbose mode, add the execution time of fixtures
Impossible to profile LoadDataFixturesDoctrineCommand
Fixtures get loaded on composer install --env=prod --no-dev
Recent releases
Similar repos
doctrine/DoctrineBundle
DoctrineBundle integrates the Doctrine ORM and DBAL (Database Abstraction...
dmaicher/doctrine-test-bundle
This Symfony bundle optimizes test performance by wrapping database drivers to...
doctrine/DoctrineMigrationsBundle
DoctrineMigrationsBundle integrates the Doctrine Migrations library into...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
doctrine/DoctrineFixturesBundle
this
|
2.5k | — | PHP | 8/10 | 3d ago |
|
doctrine/data-fixtures
|
2.9k | — | PHP | 7/10 | 3d ago |
|
doctrine/DoctrineBundle
|
4.8k | — | PHP | 8/10 | 2d ago |
|
dmaicher/doctrine-test-bundle
|
1.2k | — | PHP | 8/10 | 1mo ago |
|
doctrine/DoctrineMigrationsBundle
|
4.3k | — | PHP | 8/10 | 4w ago |
|
stof/StofDoctrineExtensionsBundle
|
1.9k | — | PHP | 7/10 | 6mo ago |
Provides raw fixture functionality; DoctrineFixturesBundle adds Symfony-specific DI and CLI integration. Not a replacement—Bundle depends on this.
Higher star count (4,838) reflects broader scope (core ORM integration). DoctrineFixturesBundle is narrower, specialized for fixtures. Complementary, not competitive.
Appears to target test-specific fixture isolation and transaction handling. DoctrineFixturesBundle is general-purpose (testing and seeding). Different use case emphasis.
Handles schema versioning; DoctrineFixturesBundle handles data. Separate concerns, often used together in same project.
Teams outside Symfony can use doctrine/data-fixtures directly. Bundle eliminates boilerplate only for Symfony users.