- What is graham-campbell/core-api used for?
- It is a lightweight foundation for exposing a consistent core API from Laravel applications, shipping an abstract API base class, interfaces, traits and helpers for config-driven HTTP calls to a single upstream Core API. Despite summaries mentioning an extensible way to serve your own services over HTTP, the code itself is a Guzzle-based client wrapper for one specific upstream. Treat it as a reference for API layering and contract design rather than a reusable component.
- Is graham-campbell/core-api compatible with Laravel 9, 10, 11 or 12?
- No. It targets Laravel 4.1 and 4.2 with illuminate 4.x constraints on PHP 5.4 through 5.6, and there is no tagged release for Laravel 5 or later. Composer will hard-conflict on a modern stack, so you cannot install it into a Laravel 9+ application.
- Can I install graham-campbell/core-api with Composer today?
- Not on any current stack, because the illuminate 4.x and PHP 5.x platform requirements block dependency resolution. There is also no maintainer producing a compatible release, since the repository lives under a GrahamDeprecated organization. The realistic path is reimplementing the equivalent 50 to 150 lines of first-party code.
- What Laravel and PHP versions does graham-campbell/core-api require?
- It requires Laravel 4.1 or 4.2 and PHP 5.4 through 5.6. PHP 5.x has had no security support since 2018, and Laravel 4.2 reached end of life even earlier. Adopting it means owning an unsupported runtime with no upstream patch path.
- Is graham-campbell/core-api still maintained?
- No. The repository sits under a GrahamDeprecated organization, which makes the abandonment explicit rather than inferred. It also has zero stars, zero dependents, and no issue triage process. Treat it as end-of-life reference material, not a dependency.
- Does graham-campbell/core-api have tests or continuous integration?
- No. The repository ships without a test suite, CI pipeline or active triage, so anything built on it is validated only by your own contract tests. That makes the undocumented upstream API, not the wrapper, the real risk surface.
- How do you configure graham-campbell/core-api?
- Configuration is a publishable config file covering the base URL, credentials and timeouts for the upstream Core API. A service provider and facade bind the client so it resolves through Laravel's container, and you subclass an abstract base class per remote service. Auth scheme, rate limits and response schemas are not specified anywhere in the sources.
- Is graham-campbell/core-api safe to use in production?
- Not in any new or maintained system. It inherits every latent CVE in an end-of-life PHP 5.x and Laravel 4.2 runtime with no patch path, and an archived repository can be deleted or its Packagist entry abandoned, silently breaking reproducible builds. That is a build-integrity concern as much as a security one.
- What should I use instead of graham-campbell/core-api for building an API in Laravel?
- Use Laravel's HTTP client through the Http facade, or Guzzle 7 directly, hidden behind an interface you own. Keep vendor quirks confined to a dedicated service or repository class so your domain code stays clean. The layering pattern the package encodes is still sound; only the implementation needs replacing.
- How do I migrate off graham-campbell/core-api?
- Start by inventorying every system that currently calls the upstream Core API through this package, since that inventory rather than the package defines the migration scope. Get an OpenAPI or JSON Schema spec, or recorded payloads, to build against, and confirm the auth model. Then reimplement the client in roughly 50 to 150 lines behind your own interface, budgeting one to three engineer-days.