- What is redot/core?
- redot/core is the foundational package for the Redot PHP/Laravel ecosystem. It provides shared core classes, a dependency injection container, HTTP routing and request handling with middleware, and utilities that other Redot packages build on. It is meant as a lightweight, modular base rather than a full-stack framework.
- Is redot/core a general-purpose Laravel package?
- No. redot/core is an ecosystem-specific foundation for the Redot Dashboard pattern, not a general-purpose Laravel library. It is appropriate only when a workstream is already committed to building on Redot; for standard Laravel product work, treat it as a reference architecture rather than a default dependency.
- How do I install redot/core in a Laravel application?
- Install it with Composer using composer require redot/core in an isolated sandbox application first. Run php artisan package:discover and php artisan about to confirm provider registration, then inspect every published config, migration, route, middleware, and asset file. Because the package is a core dependency, do not add it to a shared application branch until a timeboxed spike clears legal, version, and dependency checks.
- Which Laravel and PHP versions does redot/core support?
- The public materials do not document a supported Laravel or PHP version matrix, and there is no evidence of CI testing against specific framework versions. Composer installability alone does not prove compatibility. Verify the required PHP and Laravel versions in a disposable app and treat integration effort as unknown until that spike produces evidence.
- What license does redot/core use, and can I use it commercially?
- The repository metadata shows NOASSERTION, which is not a recognized OSI license and is not permission to use, modify, or redistribute the code. Absence of a license is a gating legal risk, not a residual one. Obtain the actual license text and written legal sign-off for internal commercial use and forking before any commitment.
- Is redot/core production-ready?
- Treat it as high risk for production. Observable adoption is effectively zero, maintainer and support signals are absent, and there is no public evidence of CI, release tags, or a security disclosure policy. Because it is a core package, a defect or Laravel incompatibility can block the entire dashboard surface, so require a sandbox spike and a fork-and-own plan first.
- What alternatives should I consider before adopting redot/core?
- For standard Laravel dashboard and admin work, benchmark against Filament, Nova, Orchid, Backpack, or plain Laravel with Blade/Livewire. Those options have documented licenses and active maintenance, which redot/core does not currently demonstrate. Choose redot/core only if your architecture is deliberately aligned with Redot Dashboard and you accept vendor-shaped coupling.
- What service providers, routes, middleware, migrations, or assets does redot/core register?
- The public documentation does not enumerate what redot/core registers on boot. You must inspect the package's service providers and any published config, route, middleware, migration, and asset files in a sandbox. Produce a written inventory of the full dependency and service-provider surface before adoption.
- Can I use redot/core in an existing Laravel app that is not Redot Dashboard?
- Technically it is Composer-installable, but architecture fit is binary: it is intended for workstreams already committed to the Redot pattern. For a non-Redot Laravel app it introduces coupling to a package your organization does not control and whose dependency graph is undocumented. If you proceed, isolate calls behind internal adapters and a dedicated DashboardServiceProvider so the codebase never calls Redot helpers directly.
- Who maintains redot/core, and what support is available?
- There is no visible maintainer signal, support path, or SLA for redot/core, and the package shows one star and zero dependents. Assume a fork-and-own model from day one and identify an internal owner before adoption. Ask whether the package is intended for public consumption or internal-only use, and document the exit cost.