Weave Code
Core Laravel Package
angel/core
Angel Core provides the foundational building blocks for the Angel ecosystem on Laravel, bundling shared contracts, base classes, service providers, and handy utilities that streamline modular application development.
angel/core is a modular foundation package for Laravel/PHP applications, providing a clean architecture for organizing reusable components and domain logic. Designed for developers who need structure without overhead, it streamlines the way core modules are registered, bootstrapped, and shared across projects.
- Modular architecture with auto-discovery and registration
- Lightweight service container integration for Laravel
- Extensible bootstrapping for reusable domain modules
- PSR-compliant, framework-agnostic core utilities
- Simple configuration for rapid package scaffolding
Frequently asked questions about Core
- Can I install angel/core with Composer in a Laravel 10 or 11 application?
- No. angel/core targets Laravel 4.2 and PHP 5.4-5.6, so Composer dependency resolution will fail against current Laravel and PHP requirements before runtime. It is not a drop-in package for modern applications. It also expects to own routes, controllers, views, migrations, and admin, which conflicts with an existing Laravel service.
- What Laravel and PHP versions does angel/core require?
- Based on its last release on 2014-09-27, angel/core aligns with Laravel 4.2, Symfony 2.4 components, and PHP 5.4-5.6. Those versions are end-of-life and do not meet the PHP 8.1+ baseline for Laravel 10, 11, or 12. Check composer.json if you fork it, but treat it as legacy-only.
- Is angel/core a library I can add to an existing Laravel service?
- No, angel/core is a full CMS application distributed as a Composer package, not a library. It supplies shared models, routing, configuration, Blade views, migrations, seeds, a theming layer, and an admin panel for pages, blog posts, menus, and users/permissions. That application ownership model makes it a poor fit for composer require into an existing Laravel service.
- What features does Angel CMS provide out of the box?
- Angel Core provides shared models, routing, configuration, and extension points used by Angel modules. It includes an admin panel covering pages, blog posts, menus, and users/permissions, plus a theming layer, migrations, and seeds. It is intended as the foundation for lightweight, customizable, content-driven sites within a Laravel 4 workflow.
- Is angel/core safe for production use?
- No, not for new or modern production. It has been unmaintained since 2014 and runs EOL Laravel 4.2, Symfony 2.4 components, and PHP 5.4-5.6. There is no security-patch channel, and abandoned transitive dependencies create supply-chain exposure. Most SOC 2, PCI, or internal vulnerability policies cannot accept it. Legacy containment with compensating controls is the only possible use, and that should still be treated as a remediation item.
- How do I migrate an existing Angel CMS site to Laravel 11 or 12?
- Treat Angel's schema and content as the specification, then stand up a current Laravel app, port the models and migrations, and rebuild routing and admin with Filament or Nova before migrating content and parallel-running. A full Laravel 4.2-to-11/12 upgrade of a CMS-sized codebase is a rewrite in all but name, so budget quarters rather than sprints. Start with a short spike to quantify breakage, inventory features actually in use, and gate each stage on a working demo.
- Does angel/core have active maintenance or community support?
- No. Its last release was 2014-09-27, it has 44 stars and zero dependents, and there is no active maintainer, release cadence, or advisory channel. Community answers are sparse and stale, and you become the sole maintainer on day one.
- What alternatives to angel/core should I consider for a Laravel CMS?
- Consider maintained CMS options on supported Laravel and PHP, such as Statamic, October CMS, Filament with a custom admin, or a headless CMS. Choose based on your actual content model, admin requirements, hosting, licensing, and team skills. Do not adopt angel/core for a greenfield project.
- Can I test angel/core on PHP 8.2 before committing to it?
- You can run a short spike in a disposable PHP 8.2 container, but expect Composer dependency resolution to fail before runtime. That result confirms the incompatibility rather than proving a fixable runtime bug. Going further requires forking, rewriting the framework-facing layer, and replacing abandoned transitive dependencies.
- Why does angel/core show a high package score if it is abandoned?
- The 0.894 score appears to measure package metadata quality, not maintenance health or security posture. It should not be read as a green light. Check the 2014 release date, Laravel 4.2 and PHP 5.4-5.6 constraints, lack of maintainer activity, and zero dependents instead.
Weaver
How can I help you explore Laravel packages today?