- What does yab/cerebrum do?
- yab/cerebrum is a Laravel and Lumen package that aims to add AI-style analysis through a configurable service provider, container binding, and Facade. It unifies language model calls, prompt handling, and embeddings behind one Laravel-friendly API. The technical evaluation describes it as a thin client adapter over a third-party AI or NLP service rather than a self-contained library.
- Is yab/cerebrum still maintained?
- No. The package is archived, has roughly 8 stars and 0 dependents, and has no active security response path. That means there is effectively no production validation or ongoing maintenance. Treat it as a reference implementation rather than a dependency you adopt directly.
- Which Laravel versions does yab/cerebrum support?
- The package explicitly mentions Lumen support and appears to target an older Laravel generation, likely Laravel 5.x through 6.x. Because it is archived, its composer.json constraints are likely stale and may conflict with Laravel 10 or 11 and PHP 8.2 and newer. Expect to need a fork or --ignore-platform-reqs on a modern baseline.
- How do I install yab/cerebrum?
- Installation is mechanically simple: composer require yab/cerebrum, publish the config file, and set the required credentials. There are no schema changes, queue workers, or infrastructure components to configure. However, you should first verify that the PHP and illuminate/support constraints resolve cleanly on your Laravel version.
- Does yab/cerebrum work with Lumen?
- Yes, Lumen support is called out explicitly. That also suggests the package targets an older service-provider registration path that predates Laravel package auto-discovery conventions. On newer Laravel or Lumen versions, registration and compatibility should be tested carefully before adoption.
- What AI provider or API does yab/cerebrum call?
- The package is described as a thin wrapper over a third-party AI or NLP or analysis API, but the upstream vendor is not confirmed in the provided context. That upstream dependency is the largest unknown because it may be deprecated, rate-limited, re-priced, or dead. A fork cannot fix vendor risk, so confirm the service is operational and publicly documented before relying on it.
- Can I use yab/cerebrum in production?
- The technical risk is high because the package is archived, has minimal adoption, and sits in a credential-bearing code path with an unmaintained transitive dependency set. Thin wrappers also commonly return null or a default on upstream errors, which can cause silent degradation in application logic. For production, reimplement the small glue layer behind a first-party interface instead of adopting the package directly.
- Is yab/cerebrum testable, or should I mock it?
- The Facade and static call style, such as Cerebrum::analyze(...), encourages direct static calls at arbitrary call sites, which is difficult to test and hard to swap later. The evaluation recommends defining your own TextAnalysis contract and implementing a vendor adapter behind it. That lets you mock the HTTP or SDK layer in tests and keep the vendor client out of application code.
- Does yab/cerebrum handle timeouts, retries, or errors?
- The provided context does not confirm any timeout, retry, or circuit-breaker handling. The evaluation notes that thin wrappers often return null or a default on upstream failure rather than throwing, creating silent-failure risk. You should assume you need your own error handling and resilience layer if you reuse the concept.
- What are good alternatives to yab/cerebrum for adding AI to Laravel?
- Treat yab/cerebrum as design inspiration rather than a dependency. Define a first-party contract such as TextAnalysis in your own namespace, implement an adapter against a currently supported SDK or plain HTTP client, and bind it in a service provider you own. This preserves the clean Facade-style ergonomics while avoiding the archived package and its stale constraints.