Weave Code
Framework Laravel Package
sokeio/framework
Sokeio Framework is a Laravel/PHP package for building modular admin panels, CMSs, and business apps with reusable components, plugins, themes, and rapid scaffolding. It streamlines backend development, customization, and extension.
Sokeio framework: Modular,Theme,User,Role,Permission
Frequently asked questions about Framework
- What is sokeio/framework and what features does it include?
- Sokeio Framework is an opinionated Laravel/PHP application framework for building modular admin panels, CMSs, and business apps. It bundles modular structure, theming, user management, and role/permission (RBAC) features into one package. It is aimed at rapid backend scaffolding and reusable components rather than being a small composable library.
- Which Laravel and PHP versions does sokeio/framework support?
- The provided evaluation does not state a specific Laravel or PHP compatibility matrix. You should inspect the package composer.json for illuminate/* and PHP constraints and compare them with your target Laravel branch. The project had a February 2025 release, but a stated policy for future Laravel major versions is not confirmed.
- Is sokeio/framework a starter kit or an installable Composer package?
- It is described as an opinionated application framework layered on Laravel and is installed as a Composer package. However, its coupling to routing, service-provider bootstrapping, theming, and auth/ACL means adoption behaves more like choosing a starter kit than adding a small component. Confirm in the README whether the intended workflow is fork-and-own or upgrade-in-place.
- Can I use Sokeio's role and permission system without adopting its modules and themes?
- The evaluation says the package bundles modules, themes, users, and RBAC as a single adoption decision, so partial use is not clearly supported. Before relying on this, verify whether the RBAC layer can run independently of the module and theme systems. If isolation is important, wrap permissions behind an internal contract such as a PermissionService so the implementation can be swapped later.
- How does sokeio/framework compare with spatie/laravel-permission, nwidart/laravel-modules, or Filament?
- Sokeio is an all-in-one framework, while spatie/laravel-permission handles RBAC, nwidart/laravel-modules handles modularity, and Filament or Orchid provide admin panel tooling. The composed approach lowers lock-in and fits brownfield apps already using those packages. Sokeio may save setup time in a greenfield admin-heavy app if its bundled modules, themes, and RBAC genuinely fit your requirements.
- Is sokeio/framework safe and actively maintained for production use?
- The evaluation flags high technical risk due to low adoption signals, including 18 stars, a 0.33 score, and a likely single maintainer. Because it touches authentication, authorization, and module bootstrapping, those security-sensitive paths have had little external review. Treat production adoption as a scoped pilot only after checking CI, test coverage, release cadence, and security disclosure practices.
- How do I install and configure sokeio/framework in a Laravel application?
- Installation is via Composer, but the provided context does not include exact commands or configuration steps. Expect config publishing, service-provider registration, middleware injection, and route registration, so follow the package README closely. Validate the result against route caching, package auto-discovery, and your existing middleware groups before expanding usage.
- Will sokeio/framework conflict with my existing Vite build, routes, or middleware?
- That is a key integration risk because the package assumes control over routing, service-provider bootstrapping, asset and theming conventions, and middleware. Test whether theme assets require a specific build pipeline or public-path assumptions that conflict with your Vite configuration. Also check for global middleware or route-file hijacking that could break an existing Laravel application.
- Can I create custom modules and themes without forking the core package?
- The README excerpt was not provided, so independent module and theme authoring is not confirmed. The evaluation recommends checking whether modules can be authored independently and whether theme assets require a specific build pipeline. If you cannot extend modules or themes without forking core, upgrade risk and lock-in increase significantly.
- What should I check before adopting sokeio/framework in an existing Laravel app?
- Do not retrofit it directly into a production monolith. Run a bounded spike in a clean Laravel skeleton pinned to your target version, then build one module, one theme, and one role/permission flow. Confirm route caching, asset compilation, auto-discovery, and middleware behavior all work before treating adoption as a scoped pilot behind a feature boundary.
Weaver
How can I help you explore Laravel packages today?