- Is endroid/guide-bundle compatible with Laravel?
- No. endroid/guide-bundle is a Symfony bundle, and its -bundle suffix follows Symfony publishing conventions that assume HttpKernel, DependencyInjection, and FrameworkBundle. Laravel has no bundle loader, so there is no supported path to install or register it in a Laravel application. Using it would require an adapter or a rewrite, not a simple wrapper.
- How do I install endroid/guide-bundle in a Laravel project?
- There is no documented Laravel installation path. The README is a single heading and contains no install instructions, configuration reference, or usage example. A Composer require would pull the code in, but nothing would register its services or routes in Laravel's container. Treat any integration attempt as custom development rather than package installation.
- What does endroid/guide-bundle actually do?
- The package is described as a Symfony bundle for adding guide functionality, meaning defining, organizing, and displaying structured help content for users. However, the repository README contains no usage details, API contract, or examples. The exact capability can only be confirmed by reading the source code. Plan on reverse-engineering behavior before you can evaluate fit.
- Is endroid/guide-bundle still maintained?
- No. The repository is archived, has zero stars and zero dependents, and shows no tests, CI, changelog, or release activity. Archiving means no upstream fixes, no security response, and no PHP or framework compatibility updates. Adopting it creates a permanent maintenance liability in your composer.lock.
- Can I use a Symfony bundle inside a Laravel application?
- Not directly. Symfony bundles rely on bundle registration in bundles.php, a Configuration tree, and container compilation passes, none of which Laravel provides. You could theoretically port specific classes if they have no Symfony dependencies, but that is a fork, not integration. In practice, treat Symfony bundles as out of scope for a Laravel stack.
- Are there Laravel packages for in-app guides and onboarding tours?
- Laravel has its own ecosystem for onboarding and product tours, and those packages are built around Blade, middleware, and service providers rather than Symfony bundles. Evaluate actively maintained Laravel-native options against your actual requirement, whether that is a first-run tour, guided setup, or in-app documentation. Do not assume endroid/guide-bundle is a candidate simply because it appears in Composer search.
- What Laravel version does endroid/guide-bundle support?
- None. The package targets Symfony, not Laravel, so there is no declared Laravel version constraint and no framework integration to test against. Its composer.json constraints would apply to Symfony components and PHP, and those have not been updated since the repository was archived. Any Laravel version claim would be unsupported.
- What are the risks of depending on an archived Composer package?
- You inherit every future bug and security issue with no upstream fix path. Archived, zero-adoption packages also create standing exceptions in dependency-review and SBOM policies, and they carry unknown blast radius when documentation is absent. For a near-zero delivered capability, that trade is rarely justified. Prefer maintained dependencies or owned code.
- Should I fork endroid/guide-bundle or build the guide feature myself?
- Forking only makes sense if the source code is substantial and directly reusable, which cannot be confirmed from the empty README. For a small onboarding or guide overlay, building in-house behind an interface you control is usually days of work, not weeks. That gives you a maintained, testable component with no external liability. Check the source first, but expect build to win.
- What license does endroid/guide-bundle use?
- It is MIT licensed, which is permissive and allows forking, modification, and sublicensing without copyleft obligations. That is the one clearly positive signal in the package. License permissiveness does not offset the abandonment and framework mismatch, but it does keep a fork legally straightforward if the code proves useful.