Weave Code
Sanjab Laravel Package
sanjabteam/sanjab
Sanjab is a Laravel admin panel package that builds dashboards, CRUD screens, widgets, and permissions from simple configuration. It bundles media management, localization, and extensible tools for creating back-office interfaces quickly, with support for Persian and other languages.
Admin panel package that I using for my projects.
Frequently asked questions about Sanjab
- Is Sanjab compatible with Laravel 10, 11 or 12?
- Sanjab is an archived package, so its Composer constraints are pinned to the Laravel and PHP versions current at archive time. A host application on Laravel 10, 11 or 12 will likely fail dependency resolution and require a fork that relaxes constraints, refreshes transitive dependencies and is re-tested. Check what a composer update actually resolves on your target version before planning integration work.
- How do I install Sanjab in a Laravel application?
- Installation follows the usual pattern: composer require sanjabteam/sanjab, publish the configuration and assets, then run the package install and migration commands. A competent Laravel developer can usually get a screening environment running in under a day. The real integration cost is version compatibility and dependency resolution, not the initial composer require step.
- Does Sanjab support multi-tenant SaaS admin panels?
- No. Sanjab is an opinionated, monolithic admin layer that mounts inside a single host Laravel application and does not provide per-tenant admin isolation or theming. Its guard and permission assumptions may conflict with tenancy requirements, so teams should validate that mapping before committing. For multi-tenant SaaS with isolated admin surfaces, it is a poor architectural fit.
- How does Sanjab generate CRUD screens from Eloquent models?
- Sanjab uses a model registry that introspects Eloquent metadata such as columns, relations and translatable fields to generate CRUD screens from configuration. Generated screens trust fillable/guarded settings and field registration, so a single misconfigured model can silently expose columns or accept over-posted attributes. Review per-field authorization and mass assignment behavior carefully on every registered model.
- Is Sanjab still maintained and safe for production?
- Sanjab is unmaintained, with no security patch channel or realistic expectation of upstream fixes, and the admin panel is the highest-value attack surface in the estate. Expect findings around generic CRUD controllers, file uploads, rich-text rendering and mass assignment. Dependency rot across its permission, translation, slugging and image libraries is the dominant risk, so a software composition analysis run should be a gate rather than a formality.
- Can I customize Sanjab's frontend UI or rebuild its assets?
- Frontend assets ship pre-compiled, so configuration and CSS overrides are the practical customization path. Any deeper UI change requires reconstructing the original Vue and Node toolchain, which may not be reproducible from what was published. Treat the UI as frozen unless you are prepared to commit to a frontend rebuild.
- What are the alternatives to Sanjab for Laravel admin panels?
- Benchmark Sanjab against a maintained alternative such as Filament before adopting it, especially on Laravel version support, security patching and community size. Sanjab's MIT license and fork-friendliness are favorable, but its small community and single maintainer mean you carry the package. The comparison should weigh long-term ownership cost, not just initial CRUD generation speed.
- How do permissions and authorization work in Sanjab?
- Sanjab uses a Spatie-style role and permission layer and relies on the host application's auth guard configuration and policies. It couples bidirectionally with the app, reaching into models and uploaded file storage while the app registers menus and widgets back into Sanjab. Because generated CRUD screens are authorization-fragile, audit guard assumptions and per-field permissions explicitly.
- Does Sanjab work with an API-first or headless Laravel backend?
- No. Sanjab is designed as an in-app admin layer for conventional Laravel monoliths with a Blade and Vue 2-era frontend, not for API-first or headless backends. It also does not fit polyglot persistence, event-driven services where the admin surface must live outside the domain app, or environments needing an independently deployed SPA admin. Coupling is high, so extracting it later is not a clean unplug.
- What license does Sanjab use and can we fork it?
- Sanjab is MIT licensed, which is permissive and fork-friendly, so you can own and modify it if you choose. A fork will need relaxed version constraints, refreshed transitive dependencies, re-testing and ongoing security patching. Before adopting, name an internal owner and team prepared to carry that maintenance for the product's lifetime.
Weaver
How can I help you explore Laravel packages today?