- Is hanson/speedy compatible with Laravel 10 or 11?
- No. The last release was 2017-12-25, which places it in the Laravel 5.4 to 5.5 and PHP 7.0 to 7.2 era. Installing it into Laravel 9, 10, or 11 with PHP 8.1+ will likely fail Composer dependency resolution or produce runtime errors. Direct production integration is not recommended; realistic options are fork-and-modernize or replace with a maintained admin package.
- What Laravel and PHP versions does hanson/speedy support?
- Based on its 2017 release date, hanson/speedy targets Laravel 5.4 to 5.5 conventions and PHP 7.0 to 7.2. You should confirm the exact version constraints in its composer.json before committing. It should not be expected to run cleanly on PHP 8 or modern Laravel releases.
- How do I install hanson/speedy in a Laravel project?
- In a legacy Laravel 5.x application, installation would typically involve requiring the package via Composer, registering its service provider and facade, publishing config and assets, and running migrations. Because the package is abandoned, pin the version and vendor it into your repository or a private Composer registry. Do not attempt a direct install in a modern Laravel application.
- Is hanson/speedy maintained or safe for production?
- There is no evidence of active maintenance, security patching, or compatibility testing against current Laravel and PHP releases. Key risks include unpatched vulnerabilities, transitive dependency advisories, Composer conflicts that block framework upgrades, and runtime fatals on PHP 8. The admin surface is often the highest-privilege part of an application, so replacement is usually the lowest total-risk production option.
- What is hanson/speedy used for?
- hanson/speedy is a Laravel admin-panel and scaffolding package intended to accelerate CRUD-style website and back-office creation. It fits a traditional Laravel monolith using Blade views, Eloquent models, and server-rendered admin screens. It does not fit an API-first, headless, or modern SPA architecture without significant adaptation.
- Can I use hanson/speedy in a headless or API-first Laravel app?
- Not without significant adaptation. The package's assumptions are tied to server-rendered Blade admin screens, bundled admin routes, published config and assets, and direct Eloquent access. For API-first or SPA architectures, use a maintained admin package or build a separate admin interface that matches your security model.
- What are alternatives to hanson/speedy for Laravel admin panels?
- Maintained options include Filament, Backpack, and Laravel Nova, depending on your budget and architecture. For an existing Laravel 5.5 application, hanson/speedy could only be evaluated as a pinned, vendored dependency in a non-critical admin module. Modern stacks should choose an actively maintained package with current Laravel and PHP support.
- Does hanson/speedy have automated tests or security audits?
- The evaluation notes a lack of automated tests, security patching, and compatibility testing against current releases. It also flags license and IP review gaps, so confirm the package is MIT-licensed and that transitive dependencies are license-compatible. The 0.995 score should not be read as a production-readiness signal; it likely reflects a ranking heuristic rather than maintenance health.
- How do I migrate from hanson/speedy to a modern Laravel admin package?
- There is no vendor-supported migration path from hanson/speedy to modern Laravel. For a legacy app, pin and vendor the package, add integration tests around admin routes, document an exit plan, and isolate the admin panel behind SSO, VPN, or a separate subdomain with least-privilege database access. Rebuild required CRUD, auth and roles, audit logging, file uploads, reporting, and workflow features in a maintained package such as Filament, Backpack, or Laravel Nova.
- What are the risks of using an abandoned Laravel package like hanson/speedy?
- Abandonment risk is high: no security patching, Composer conflicts that can block framework upgrades, PHP 8 runtime fatals, and undocumented assumptions about authentication, authorization, mass assignment, and database schema. The blast radius is the admin surface, which is often the highest-privilege part of the application. You need an internal owner willing to fork, patch, and maintain the package, plus a clear exit plan and replacement candidate.