Weave Code
Rad Bundle Laravel Package
smart-core/rad-bundle
smart-core/rad-bundle is a Laravel package offering rapid application development tooling—scaffolding, conventions, and utilities—to help build CRUD and admin features faster while reducing boilerplate.
Rapid Application Development for Symfony
Frequently asked questions about Rad Bundle
- Is smart-core/rad-bundle a Laravel package?
- No. Despite appearing in Laravel-oriented package listings, smart-core/rad-bundle is a Symfony bundle. It registers services into Symfony's DI container, hooks HttpKernel events, and ships Bundle, Extension, and CompilerPass classes discovered through config/bundles.php. None of those mechanisms exist in Laravel, so it cannot be dropped into a Laravel application as a normal dependency.
- Can I install smart-core/rad-bundle in a Laravel application?
- Composer may resolve the package, but integration feasibility is low because the gap is a framework-paradigm gap rather than an adapter gap. The realistic options are running it as a separate Symfony sidecar and integrating at HTTP or queue boundaries, or porting its generator templates and conventions into Laravel-native Artisan commands. Shimming Laravel's container to Symfony's ContainerInterface and running Doctrine beside Eloquent is a two-ORM, two-container application with subtle failure modes and should be avoided.
- What are the Laravel alternatives for rapid CRUD and admin scaffolding?
- If your requirement is rapid CRUD and admin scaffolding rather than this specific bundle, Laravel-native options clear the maintenance bar this package fails. Consider Filament for admin panels, Laravel Nova for a paid and supported solution, Backpack or Orchid for other admin approaches, or thin first-party Artisan generators tailored to your conventions. All of these avoid a cross-framework port and inherit active maintenance, documentation, and community troubleshooting.
- Which PHP and Symfony versions does smart-core/rad-bundle support?
- The evaluation found no evidence of release tags, a CI status matrix, static analysis, or a declared support window, so version support must be verified directly in the repository's composer.json before any decision. Given the package's vintage, expect it to target older Symfony 2 or 3 era releases rather than current versions. Check for a green CI matrix on the PHP and Symfony versions you actually run, and assume nothing beyond what composer.json explicitly declares.
- Is smart-core/rad-bundle actively maintained?
- There is no evidence of an active maintenance cadence. The package shows zero stars, zero dependents, and zero Packagist installs, which means no production usage to inherit bug reports from, no troubleshooting corpus, and no third-party scrutiny of the code. No security disclosure policy was found either. For a generator that writes files into your application, abandonment is not neutral; it silently accumulates drift against newer PHP and framework versions.
- Does smart-core/rad-bundle hard-depend on Doctrine, Twig, and Symfony Form?
- A RAD bundle of this kind typically binds its generators to Doctrine entities, Symfony routing, Twig, and Symfony Form, each of which maps to a different Laravel counterpart such as Eloquent, route files, Blade or Inertia, and Form Requests. Whether the ORM layer is abstracted is not established by the available information. Inspect composer.json for hard dependencies before assuming any layer is swappable, because an ORM-agnostic claim that is not backed by an abstraction is effectively a Doctrine dependency.
- What exactly does the scaffolding generate, and can it be regenerated?
- Expect generated config, PHP classes, migrations, and templates, though the exact output should be confirmed by running the generator in an isolated project. The critical question is whether output is edited in place, which is fork-on-write, or regenerated idempotently. Fork-on-write output permanently embeds the package's conventions in your codebase even after the dependency is removed, so that distinction drives long-term ownership cost.
- How should I evaluate smart-core/rad-bundle safely before committing?
- Treat it as prior art for the rapid CRUD category rather than a candidate dependency for a Laravel codebase. Stand it up in a throwaway Symfony project, run the generators, and read the emitted files to judge whether the conventions are worth porting. Check release history, CI status, and the maintainer of record before relying on anything. If you only need the ideas, porting templates into your own Artisan commands gives you the value without the dependency risk.
- Can I run smart-core/rad-bundle as a sidecar service next to a Laravel app?
- Yes, that is the lowest-effort viable path. Run the bundle inside a separate Symfony service and integrate with your Laravel application at HTTP or queue boundaries. The tradeoff is that the RAD value stays confined to that service, so you maintain two stacks and two deployment pipelines. It is still preferable to mixing containers and ORMs inside a single application.
- Does the MIT license make smart-core/rad-bundle safe to adopt?
- The MIT license removes legal friction, but it mitigates none of the technical risk. Zero adoption, unknown maintenance cadence, no visible CI or security policy, and a framework mismatch in the registry metadata all remain. License permissiveness is a necessary condition for adoption, not evidence of fitness, so weigh the technical signals separately from the license terms.
Weaver
How can I help you explore Laravel packages today?