barryvdh/reflection-docblock
Fork of phpDocumentor ReflectionDocBlock for laravel-ide-helper. Parses PHPDoc DocBlocks to extract descriptions, tags, and types, working like PHP’s Reflection. Use to read getDocComment() from classes/methods or raw DocBlock strings.
Architecture fit: Poor. This is a fork specifically tailored for laravel-ide-helper with explicit discouragement of other uses in the README. The official phpDocumentor/ReflectionDocBlock is the standard for PHPDoc parsing, making this fork unnecessary for general Laravel applications.
Integration feasibility: Low. The package is designed solely as a dependency for laravel-ide-helper and lacks documentation for standalone use. Direct integration into new projects would violate the maintainer's guidance.
Technical risk: High. Zero direct dependents, a future-dated release (2026-03-05), and no active community adoption indicate abandonment or experimental status. Potential for unresolved bugs in edge cases (e.g., generics, callable types) due to limited testing scope.
Key questions: Why was this fork created when the official package exists? What specific fixes or features does it provide that the official version lacks? Is there any active maintenance or community support for this fork?
Stack fit: Not recommended for any Laravel project outside of laravel-ide-helper's internal usage. The official phpDocumentor/ReflectionDocBlock (v5.x+) is the only production-ready solution for PHPDoc parsing in Laravel ecosystems.
Migration path: Replace this package with phpdocumentor/reflection-docblock (v5.3+). The official package has identical core functionality, broader compatibility, and active maintenance.
Compatibility: High risk of parsing inconsistencies. The fork has diverged from the official package (e.g., ContextFactory additions in v2.3.0), but these changes are undocumented and untested for general use.
Sequencing: Avoid adoption entirely. If already used (e.g., via laravel-ide-helper), ensure the dependency is pinned to the version required by that package and do not expose it to application code.
Maintenance: Minimal effort required to maintain but high long-term risk. No community contributions or issue resolution activity
How can I help you explore Laravel packages today?