- Is raphy/markdown-bundle compatible with Laravel?
- No. It is a Symfony bundle built around a bundle registration class, a DependencyInjection extension, and Resources/config service definitions, none of which map onto Laravel's service-provider, facade, or publishable-config model. Out-of-the-box fit with a Laravel codebase is effectively zero. For Laravel, use league/commonmark directly or Laravel's built-in Str::markdown() helper, which is already built on commonmark.
- How do I install raphy/markdown-bundle?
- You would run composer require raphy/markdown-bundle and register RaphyMarkdownBundle in your Symfony kernel's bundle list. On a current stack Composer will most likely refuse the install because of the bundle's PHP and symfony/* version constraints, which date from 2018. Check the declared constraints in composer.json before planning any integration work.
- Which PHP and Symfony versions does RaphyMarkdownBundle support?
- The bundle follows pre-Symfony-5 conventions, so expect PHP 7.x-era and Symfony 3 or 4 constraints. It is not verified to install under PHP 8.2 or 8.3, and its symfony/* requirements will likely conflict with modern framework components. Confirm the exact constraints against your target runtime before relying on it.
- Is raphy/markdown-bundle still maintained?
- The last release was 2018-06-04, roughly seven years ago, with no PHP 8 fixes and no issue triage since. Adoption is essentially nil at about 4 GitHub stars and 0 dependents, so there is no community to absorb bugs or publish patches. Treat it as abandoned and budget for owning any defect yourself.
- How does raphy/markdown-bundle render Markdown to HTML?
- It registers container services and template helpers that convert Markdown strings into HTML, intended for docs, CMS articles, and other lightweight markup content. The bundle itself is dependency-injection glue around a standalone Markdown parser; the parser, not the wrapper, is the reusable engineering asset. If you adapt it, instantiate the parser directly in a service provider and treat the bundle as reference code.
- Is raphy/markdown-bundle safe for user-submitted Markdown?
- Rendering is a security-relevant surface: if raw HTML passthrough is enabled by default, unescaped output on user-submitted content is a stored-XSS vector. Audit the default configuration rather than assuming it is safe, disable raw HTML where possible, and sanitize rendered output. A 2018 codebase with no maintenance also has no security response process behind it.
- What should I use instead of raphy/markdown-bundle in a Laravel app?
- Use league/commonmark, which is actively maintained, extension-driven, and already the substrate for Laravel's own Str::markdown() helper. For basic needs Str::markdown() removes an entire class of integration work. Parsedown is another option but is less actively developed, so evaluate commonmark first.
- Can raphy/markdown-bundle still be used in a Symfony application today?
- It is technically native to Symfony on a matching major version, but it remains an orphaned dependency with no upgrade path to a current release. Composer will likely block installation on Symfony 5, 6, or 7 and on PHP 8.x runtimes. Wiring league/commonmark into a Symfony service is the lower-risk path even in its native ecosystem.
- Does raphy/markdown-bundle have tests and CI coverage?
- Test coverage and CI status at the last commit are unverified, and there are no recent CI runs against supported PHP versions. Assume no coverage guarantees and no regression safety net if you adopt or fork it. The small surface area limits exposure but does not eliminate the risk.
- Should I fork raphy/markdown-bundle?
- The MIT license and small surface area make a fork legally and technically straightforward. However, forking means you own PHP 8 compatibility, security review, and any staleness inherited from the underlying parser, which you cannot upgrade independently of the wrapper. Only fork if a specific behavior here is genuinely unique; otherwise extract that piece or migrate to league/commonmark with snapshot tests proving rendered-HTML parity.