Integration bundle for DoctrineExtensions by l3pp4rd in Symfony
1.9k
Stars
382
Forks
37
Open issues
30
Contributors
AI Analysis
StofDoctrineExtensionsBundle integrates DoctrineExtensions (a library of ORM/ODM behaviors and utilities) into Symfony projects, enabling features like timestamping, slugs, tree structures, and soft deletes. It serves developers building Symfony applications with Doctrine who need common database entity behaviors without implementing them manually. This is a specialized integration layer for the Symfony/Doctrine ecosystem, not a general-purpose tool.
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.
Symfony integration layer for DoctrineExtensions, providing extensible ORM behaviors since 2010
StofDoctrineExtensionsBundle bridges Symfony and DoctrineExtensions, a collection of Doctrine ORM behaviors (timestamps, slugs, tree structures, soft deletes, etc.). It serves Symfony projects that need common database entity patterns without writing boilerplate. The bundle has been a stable dependency in the Symfony ecosystem for 15+ years, with adoption appearing concentrated among established Symfony applications rather than new projects.
Created in 2010 when Symfony 2 adoption was rising and ORM extension patterns were being standardized. The bundle became the canonical way to integrate l3pp4rd's DoctrineExtensions library into Symfony applications, establishing itself as foundational infrastructure rather than a feature-driven project.
Growth plateaued years ago: 1,929 stars represents modest but stable community awareness rather than recent traction. The project has not gained stars in the last 7 days and shows no acceleration signals. This reflects maturity in a solved problem space — the bundle likely reached saturation among its target audience (Symfony teams using Doctrine ORM) and remains maintained rather than actively expanded.
Adoption not formally verified in README, but indirect signals exist: 1,929 stars and 382 forks suggest sustained community presence. The bundle is listed on Packagist (mentioned in README) and documentation is hosted on symfony.com, indicating official recognition within the Symfony project. Real-world adoption appears likely among established Symfony/Doctrine applications, but concrete production deployment evidence is not documented.
Based on README, the bundle acts as a Symfony integration layer for DoctrineExtensions, likely providing configuration, service registration, and event listener wiring. No architectural details are documented in the provided README excerpt beyond stating it is an 'integration bundle.' Likely follows standard Symfony bundle patterns (DependencyInjection, Configuration, EventDispatcher integration).
Not documented in README.
Last push on 2026-01-23 (approximately 5 months prior to analysis date 2026-07-03) indicates recent maintenance activity. This is not stagnant; the project appears actively maintained at a low-churn cadence appropriate for stable infrastructure. However, the lack of star growth and minimal recent activity suggests no new feature development, only dependency and compatibility updates.
ADOPT IF: your Symfony application uses Doctrine ORM and needs common entity patterns (soft deletes, timestamps, slugs, tree structures) without writing custom listeners, and you prefer a well-established integration over custom code. AVOID IF: you are using Doctrine without Symfony, prefer minimal dependencies, or need newer ORM patterns Doctrine 2.x/3.x may address natively. MONITOR IF: you are evaluating Symfony 7+ or Doctrine 3.x compatibility, as the bundle's last update was early 2026 and forward compatibility should be verified.
Independent dimensions
Mainstream potential
2/10
Technical importance
6/10
Adoption evidence
4/10
- Dependency on both Symfony and DoctrineExtensions — incompatibilities in either upstream project could require maintenance without guaranteed fixes.
- Limited recent feature development (last push early 2026, no star growth) suggests the maintainer may not be actively expanding functionality; critical bug fixes may face delays.
- Documentation exists on symfony.com but README excerpt is minimal — deeper implementation details and edge cases may require external documentation or code inspection.
- Adoption appears concentrated in existing Symfony/Doctrine projects rather than growing new adoption — younger projects may be exploring alternatives or native Doctrine features.
- No evidence of active community contribution or discussion — adoption not verified in public forums or case studies.
Likely to remain a stable, low-maintenance component for existing Symfony/Doctrine users. May face gradual adoption decline if Doctrine 3.x and Symfony 7+ incorporate native extension patterns, but will probably persist as a maintained compatibility layer for legacy applications.
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
- 6mo ago
- Created
- 191mo 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
loggable and doctrine migrations
ext_translations table not generated
Metadadata cache generates empty files each timefor Loggable and Softdeleteable
Doctrine event listener and softdeleted filter
Translatable doesn't work
Top contributors
Similar repos
doctrine/DoctrineBundle
DoctrineBundle integrates the Doctrine ORM and DBAL (Database Abstraction...
doctrine-extensions/DoctrineExtensions
Doctrine Extensions is a collection of behavioral extensions for Doctrine ORM...
doctrine/DoctrineMigrationsBundle
DoctrineMigrationsBundle integrates the Doctrine Migrations library into...
doctrine/DoctrineFixturesBundle
DoctrineFixturesBundle integrates Doctrine Data Fixtures into Symfony...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
stof/StofDoctrineExtensionsBundle
this
|
1.9k | +1 | PHP | 7/10 | 6mo ago |
|
doctrine/DoctrineBundle
|
4.8k | — | PHP | 8/10 | 2d ago |
|
doctrine-extensions/DoctrineExtensions
|
4.1k | — | PHP | 8/10 | 3mo ago |
|
doctrine/DoctrineMigrationsBundle
|
4.3k | — | PHP | 8/10 | 4w ago |
|
doctrine/DoctrineFixturesBundle
|
2.5k | — | PHP | 8/10 | 3d ago |
 dmaicher/doctrine-test-bundle
|
1.2k | — | PHP | 8/10 | 1mo ago |
StofDoctrineExtensionsBundle is a wrapper; DoctrineExtensions (4,143 stars) is the underlying library. The bundle adds Symfony-specific configuration and service wiring but does not replace the core library.
Doctrine ORM (10,173 stars) provides base persistence; DoctrineExtensions/bundle add convenience behaviors (slugs, timestamps, soft deletes). ORM alone is more fundamental; the bundle addresses extension patterns ORM does not natively provide.
Alternative is writing timestamps, soft-delete logic, and slug generation directly in entity classes. The bundle trades a dependency for reduced boilerplate and standardized behavior.
StofDoctrineExtensionsBundle is less widely adopted (1,929 vs 2,923 stars for MonologBundle) but serves a narrower, specialized need (ORM extension patterns vs. logging/debugging infrastructure).
