- Can I use gigadrive/markdown-wiki-bundle in a Laravel application?
- Not directly. Despite being described as a PHP package, this is a Symfony 5 bundle that registers through Kernel::registerBundles, a DependencyInjection extension, and a TreeBuilder config tree, none of which exist in Laravel. There is no published Laravel service provider or wrapper, and the package has zero dependents, so no integration path has been proven even experimentally. Using it in Laravel means forking it and re-hosting its controllers, routes, and views under Laravel conventions, at which point you own the code.
- Does gigadrive/markdown-wiki-bundle support Laravel 10 or Laravel 11?
- Almost certainly not. The bundle targets Symfony 5, and modern Laravel versions require Symfony 6 or 7 components, so Composer will likely resolve only against Laravel 8 or 9-era stacks. The v1.3.1 release notes contain no compatibility statement, so assume the composer.json constraints were not widened. Installing it in a current Laravel app would drag your dependency tree backwards.
- How do I install gigadrive/markdown-wiki-bundle?
- In a Symfony 5 app you require it with Composer, register the bundle in config/bundles.php, and configure the extension through a Symfony config file. Documentation is thin, so verify the exact configuration keys against the repository before wiring anything up. There is no Laravel installation path and no artisan publish command to follow.
- What is gigadrive/markdown-wiki-bundle actually used for?
- It turns a folder of Markdown files into browsable dynamic subpages, handling routing, parsing, and templating for you. It is aimed at help sections and small wikis inside existing Symfony 5 applications. The genuinely reusable parts are the Markdown renderer, likely league/commonmark, and the page-resolution logic.
- Is gigadrive/markdown-wiki-bundle still maintained?
- It is dormant rather than clearly abandoned. A v1.3.1 patch appeared after a multi-year gap, which proves someone can still tag and publish, but one patch release is not a maintenance cadence. There is no stated security-response process, and with 3 stars and 0 dependents there is no community to borrow confidence from.
- Is it safe to serve a Markdown wiki from a folder on disk?
- That depends entirely on your implementation. Dynamic subpages mean a slug is resolved to a file, so strict slug validation and realpath containment are mandatory to prevent path traversal. If editor-authored Markdown is rendered with raw HTML allowed, you also need html_input escaping to avoid stored XSS. The v1.3.1 fix for a wrong file permission level sits exactly in that file-resolution path and is a reason to audit rather than relax.
- What is the security advisory mentioned in gigadrive/markdown-wiki-bundle v1.3.1?
- The release notes say security updates but give no CVE, no GHSA advisory ID, no affected-version range, and no description, so the blast radius cannot be triaged. Obtain the advisory ID and the diff before this package is considered for anything. An unannounced, unfixed class of defect carries the same risk as an archived repository.
- What are the alternatives to this package for a Markdown wiki in Laravel?
- In Laravel you are better served by league/commonmark directly, wrapped in a route and a Blade view, or by a Laravel-native documentation package. Even on Symfony, note that Symfony 5.x is end-of-life, so a newer LTS is warranted regardless. The framework-agnostic parser is the part worth adopting; the bundle scaffolding is not.
- How would I build a Markdown wiki in Laravel myself?
- Add league/commonmark, define a route with a constrained slug parameter, resolve that slug against a whitelisted directory, and render through CommonMark's HtmlRenderer configured to escape raw HTML. Cache the rendered output and invalidate it when the underlying file changes. This is usually a few dozen lines of code and removes a barely-maintained dependency entirely.
- Does gigadrive/markdown-wiki-bundle support PHP 8.2 or 8.3?
- This is unverified. Neither the release notes nor the repository provide a compatibility statement, and the bundle's Symfony 5.x dependency is end-of-life. Test against your target PHP version before relying on it, and expect that any security issue inside that dependency tree will not be patched here.