- What is folklore/laravel-folklore used for?
- It is a Laravel-native foundation for adding reusable domain behavior to an application, including domain contracts, entities, repositories, and a JsonDataCast. It also bundles feature modules such as pages and blocks, media through folklore/laravel-mediatheque, users with a custom repository auth provider, third-party glue, and make generators. It is best understood as an opinionated application foundation rather than a small utility library.
- Which Laravel and PHP versions does folklore/laravel-folklore support?
- The package's AGENTS.md specifies PHP ^8.3 and Laravel 11 through 13, so read composer.json as the source of truth. The repository description calling it a Laravel 5 package is stale metadata and should not be used for planning. Laravel 11 and 12 sites remain on Guzzle 7, while Laravel 13 sites can use Guzzle 8.
- How do I install folklore/laravel-folklore in a Laravel app?
- Install it with Composer using composer require folklore/laravel-folklore. Laravel auto-discovery registers the package without manual service provider edits, and you only need to publish the configuration if you want to tailor its behavior. Check the repository README for any additional setup steps and usage details.
- Can I use folklore/laravel-folklore on Laravel 10 or PHP 8.2?
- No, the runtime constraints are current rather than legacy: PHP ^8.3 and Laravel 11 through 13. Any estate still on Laravel 10 or PHP 8.2 must upgrade first, and that should be treated as a prerequisite project. This is not a routine line item in an installation checklist.
- What Guzzle version does folklore/laravel-folklore require?
- Version 1.1.7 supports Guzzle ^7.15.2 or ^8.0.1, with Guzzle 8 available only on Laravel 13. The minimums are deliberately pinned to include the fix for GHSA-v5mv-p594-2x33, which the media download host checks depend on. Check your dependency floor against these versions in Phase 0, because a routine patch bump may become a mandatory upgrade.
- Is folklore/laravel-folklore a general-purpose Laravel package?
- No, it is the shared application foundation for sites built by one agency and is an opinionated framework layered on Laravel. It fits a Laravel app that intends to be a Folklore-shaped app with an entity/repository pattern, pages and blocks, and mediatheque-backed media. For other codebases, use Laravel-native patterns or narrower packages instead of adopting the whole foundation.
- Can I use only some folklore/laravel-folklore modules without Customer.io or PubNub?
- The stated design intent is that a module a site does not use must cost it nothing, with no side effects at boot and no heavy mandatory dependency. However, the technical evaluation says this is the single most important thing to verify, and the v1.1.7 notes do not prove unused modules are free at boot. Test boot behavior and dependency loading before adopting a single module in an app that will not use Google, PubNub, or Customer.io.
- Is the custom repository auth provider in folklore/laravel-folklore safe for production?
- It replaces Laravel's Eloquent user provider with a repository provider, which is a security-sensitive change touching login, password reset, remember-me, and session invalidation. Treat it as needing its own threat model and regression suite rather than a standard code review. Vet it carefully before using it in production authentication.
- How does folklore/laravel-folklore support testing and CI?
- The package exposes a test-friendly API that works with Laravel's testing helpers. Its CI now includes lowest-accepted Guzzle 7 and Guzzle 8 runs and prints installed Guzzle versions per job, which helps surface dependency-floor conflicts early. You should still add application-level regression tests for the modules and auth behavior you enable.
- Who maintains folklore/laravel-folklore and is there community support?
- It is a Folklore agency package, and the evaluation notes zero stars and zero tracked dependents, meaning there is no broad community or public issue history to mine. Distribution and community support are therefore still blockers for some teams. Plan for vendor reliance and direct maintainer contact rather than assuming an active open-source ecosystem.