Weave Code
Core Laravel Package
amethyst/core
Amethyst Core provides the foundational Laravel/PHP building blocks for the Amethyst stack, including service providers, shared contracts, configuration, and common utilities. Lightweight and extensible, it keeps shared concerns consistent across Amethyst packages and applications.
At a glance
Frequently asked questions about Core
- What is amethyst/core used for?
- Amethyst Core is the kernel layer of the Amethyst micro-framework. It supplies the application, HTTP, and console kernels, a service-provider registry, and a configuration repository modeled on Laravel's bootstrap lifecycle. It is not a general-purpose component library; its value only appears if you adopt the full Amethyst stack with routing, HTTP, and console packages.
- Is amethyst/core a Laravel package?
- No. amethyst/core is the kernel of the Amethyst micro-framework, not a Laravel package. It deliberately mirrors Laravel concepts such as service providers and config repositories but does not integrate with Illuminate\Foundation. In a Laravel application it is redundant.
- Does amethyst/core work with Laravel 10 or 11?
- There is no Laravel 10 or 11 support to evaluate because amethyst/core does not target Laravel. It overlaps almost entirely with Laravel's own kernels, container, and ServiceProvider. For any Laravel version, use Laravel's native foundation components instead of adding this package.
- How do I install amethyst/core and which PHP versions does it require?
- Install it with Composer using composer require amethyst/core, but first check the target branch's composer.json rather than the README. Expect PHP 7.x-era constraints and dependencies on Zend Framework components that were later renamed to Laminas. Installing core alone gives you kernels and a container, not routing or an HTTP message implementation.
- Is amethyst/core still maintained?
- Effectively no. The repository has negligible adoption, no meaningful release cadence, and a bus factor of one. There is no production corpus, issue history, or community tutorial base to rely on. Any defect or security issue would become an internal patch.
- What are the best alternatives to amethyst/core for a PHP service?
- For a standalone PHP service, use Symfony HttpKernel with PSR-15 middleware and a maintained PSR-11 container. That delivers the same architectural pattern with an active security posture. For Laravel, the correct alternative is Laravel's own Illuminate\Foundation, container, and ServiceProvider.
- Can I reuse only the service provider and config repository from amethyst/core?
- The MIT license allows you to lift individual classes, but the service-provider registry and config repository are thin and tied to Amethyst conventions. In Laravel, use the native ServiceProvider and Repository implementations. In a standalone service, prefer maintained PSR-11 containers and dedicated config libraries instead of copying framework code.
- Is amethyst/core safe for production?
- Treat it as high risk for production. Adoption is effectively zero, the project is dormant, and transitive Zend-to-Laminas dependency decay can pin you to end-of-life PHP runtimes with unpatched CVE exposure. The MIT license is clean, but the engineering and supply-chain risk is severe unless you already operate an Amethyst codebase.
- How do I test an application built on amethyst/core?
- There is no documented community test harness or corpus for amethyst/core, so you must build your own. The kernels and provider registry are plain PHP, so providers and config access can be unit-tested with PHPUnit. For HTTP-kernel behavior, use PSR-7 request and response doubles and expect to maintain that test infrastructure yourself.
- How do I migrate an existing Amethyst application off amethyst/core?
- Freeze new framework-level investment and inventory every class that touches amethyst/core kernels, providers, and config access. Replace the config repository first with a PSR-compatible equivalent, then the container, and the HTTP kernel last. Ship each step behind the existing bootstrap so the application remains deployable throughout.
Weaver
How can I help you explore Laravel packages today?