- How do I install larva/laravel-settings in a Laravel application?
- Install it with Composer using composer require larva/laravel-settings. The package is described as a Laravel Composer package, so installation is mechanically a Composer require plus optional service provider registration if the package does not use auto-discovery. The provided context does not include a full installation guide, configuration publishing steps, or migration commands, so verify those in the repository before adopting it.
- Which Laravel and PHP versions does larva/laravel-settings support?
- The provided context does not state supported Laravel or PHP versions. The only release information available is a single release dated 2023-03-10, which raises compatibility questions for current Laravel versions. Check the package's composer.json constraints and test matrix before using it in a modern Laravel app.
- Is larva/laravel-settings maintained and safe to use in production?
- The available assessment flags significant maintenance and production-risk concerns: zero stars, zero dependents, no issue traffic, no documentation, and a last release in March 2023. There is no evidence of production use or community security review. For production, treat it as unproven until you review the source, tests, license, and compatibility yourself.
- What license is larva/laravel-settings released under?
- The repository license is reported as NOASSERTION, meaning the license could not be identified from the repository metadata. That is a blocker for commercial or distributed codebases until legal has a clear written license grant. Ask the maintainer to publish an explicit LICENSE file before adopting the package.
- Does larva/laravel-settings support typed settings classes?
- The package blurb says it stores typed configuration in the database and exposes values through a clean API, which suggests typed settings are part of the intended design. However, the technical assessment notes that typed settings classes are asserted rather than demonstrated in the available documentation. Review the source or README for concrete examples of typed setting classes before relying on that feature.
- How does caching work in larva/laravel-settings, and will it work with Redis or Octane?
- The blurb states the package keeps performance fast with built-in caching, but the available context does not describe the cache invalidation strategy or cache store integration. It is not confirmed whether it works cleanly with Redis or long-running workers such as Laravel Octane, where in-process caching can serve stale values. Verify the caching implementation and cross-process invalidation behavior in the source before using it in queued or Octane environments.
- Can I use larva/laravel-settings for multi-tenant Laravel applications?
- The provided context does not confirm per-tenant scoping or any tenancy model support. Multi-tenant use would require verifying how settings are keyed, scoped, and isolated per tenant in the package's data model. Do not assume tenant isolation until the source and schema are reviewed.
- Does larva/laravel-settings support encryption for secret settings?
- Encryption at rest for secrets is not confirmed in the available information. The assessment explicitly lists encryption for secrets as an unverified capability. If you need to store API keys or credentials, confirm whether the package encrypts values or whether you must handle encryption yourself.
- How does larva/laravel-settings compare to spatie/laravel-settings?
- spatie/laravel-settings is described in the assessment as the known-good alternative with an established, documented contract. larva/laravel-settings has a similar stated purpose of database-backed, typed, cache-backed settings, but lacks verifiable documentation, adoption, and maintenance signals. For a platform-wide dependency, the established package is the lower-risk baseline unless source review of larva/laravel-settings proves otherwise.
- Does larva/laravel-settings have tests and CI, and how do I migrate existing settings into it?
- The available context reports no CI badge, no coverage signal, and no documentation, so its test posture is unknown. A migration path from config files, environment variables, or a custom settings table is also not documented; adoption would require schema alignment, a one-time backfill, and rewriting code to the package's API. Ask the maintainer for the test suite, CI pipeline, and migration guidance before planning adoption.