Weave Code
Core Laravel Package
kreta/core
kreta/core is the foundational package for the Kreta Laravel ecosystem, providing shared contracts, service providers, configuration, and utilities that other Kreta modules build on. It offers a consistent base for integrating and extending Kreta-based applications.
Kreta core component
Frequently asked questions about Core
- What is kreta/core used for?
- kreta/core is the shared foundation for Laravel applications built on the Kreta ecosystem. It bundles base classes, contracts, service providers, DTOs, value objects, and reusable traits so sibling Kreta packages and application code can share common conventions. It is intended as a platform-level dependency rather than a standalone feature package.
- How do I install kreta/core?
- Install it with Composer as you would any Laravel package. The registry listing does not surface version constraints, so confirm the available release and its Laravel and PHP requirements before adding it to composer.json. Then run composer require and check whether its service provider is auto-discovered or must be registered.
- Does kreta/core support Laravel 10 or Laravel 11?
- The package description says it integrates with Laravel's container, config, and validation, but the available metadata does not show explicit illuminate/* constraints or which Laravel majors are tested. Treat Laravel version support as unverified until you inspect composer.json or CI configuration. Test the exact Laravel and PHP versions you plan to use before committing.
- Is kreta/core production ready?
- The registry signals are weak: zero stars, zero dependents, and no surfaced version history, license, or maintainer activity. That does not prove it is unusable, but it does mean downstream production use has not been visibly validated. Run an isolated install spike and review the code before relying on it in production.
- Is kreta/core actively maintained?
- The available evidence does not show commit cadence, release tags, or maintainer activity. The TPM assessment flags single-maintainer stall as a high-likelihood, high-impact risk for a core package. Ask the maintainer directly or check the repository history before adopting it.
- What license does kreta/core use?
- The registry excerpt does not surface a license. License compatibility can be disqualifying depending on your distribution model, so confirm it before a spike or proof of concept. Do not assume MIT or any other license without checking the repository and composer.json.
- Can I use kreta/core without other Kreta packages?
- The package is described as the foundation other Kreta modules build on, so it may stand alone mechanically but provide limited value without sibling packages. It is unclear from the listing whether it hard-requires other Kreta packages or fails loudly when they are absent. Verify its composer requirements and test a standalone install.
- What alternatives exist to kreta/core?
- If you are not committed to the Kreta ecosystem, a core package like this is an architectural choice rather than a utility swap. Alternatives include building your own shared Laravel package foundations or using well-established Laravel starter kits and package skeletons. Evaluate whether Kreta's domain model matches your application before comparing alternatives.
- Does kreta/core include DTOs and value objects?
- Yes, the package description lists typed DTOs and value objects as part of its shared foundation. It also includes base classes, contracts, service providers, helpers, and reusable traits. The exact API and stability of those classes are not documented in the available metadata.
- How should I test kreta/core in a Laravel app?
- Start with an isolated install in a throwaway Laravel application on your target PHP and Laravel versions. Check service provider auto-discovery, config publishing, container bindings, and whether any global middleware or bootstrapping leaks into unrelated parts of the app. Add a small integration test that exercises the DTOs, contracts, and any extension points you depend on.
Weaver
How can I help you explore Laravel packages today?