- What is krystal-sf/common used for?
- It is described as common files and shared utilities for Krystal Symfony projects, with a blurb claiming Laravel and PHP support. It provides helpers, traits, base classes, service providers, and config scaffolding intended to standardize conventions across projects. Verify the actual framework dependencies before adopting it.
- Is krystal-sf/common a Laravel package or a Symfony package?
- The repository slug and prior review material say it is for Krystal Symfony projects, but the supplied description mentions Laravel and standalone projects. The composer.json require block (illuminate/* vs symfony/*) settles this. Plan for Symfony by default until confirmed otherwise.
- How do I install krystal-sf/common with Composer?
- If it is published on Packagist, run composer require krystal-sf/common. If it is not published, you would need a vcs or path repository entry pointing at Krystal's GitLab, which introduces third-party credentials and availability into your build. Check for tagged releases and a license first.
- Does krystal-sf/common support Laravel 10 or Laravel 11?
- There is no confirmed Laravel version support in the provided context. The package may require symfony/* instead of illuminate/*, which would make Laravel integration inert. Review composer.json constraints and test against your target Laravel version before relying on it.
- Is krystal-sf/common available on Packagist?
- The context does not confirm Packagist availability. It may only resolve from Krystal's private GitLab via a VCS or path repository. If it is not published, ask why and treat that as a supply-chain and maintenance risk.
- What license does krystal-sf/common use?
- No license is visible in the metadata. Unlicensed code is all rights reserved by default, which blocks commercial use and modification without explicit permission. Confirm a LICENSE file and its terms before using it in production.
- Is krystal-sf/common actively maintained?
- There is zero stars, zero dependents, and no visible release signal in the context. You would likely be the first external consumer, with no community triage for defects. Ask Krystal for tagged releases, cadence over the last 12 months, and an owner committed to external consumers.
- What are alternatives to krystal-sf/common for shared Laravel utilities?
- For Laravel applications, use illuminate/support helpers, Laravel's own traits and base classes, or well-maintained packages like laravel/framework components. For cross-project conventions, consider an internal shared-foundation package with your own tests and license headers. Re-implementing the small helper surface is often faster than adopting an unverified dependency.
- Can I use krystal-sf/common in production?
- Only after discovery confirms a commercial-friendly license, tagged releases, framework compatibility, and a named maintainer. The current posture is a reading task, not an integration task. Most dependency allow-lists would reject an unpublished third-party VCS dependency with zero dependents.
- How do I test krystal-sf/common in a Laravel app?
- First confirm whether it requires illuminate/* or symfony/*. If Symfony-only, the service providers and container wiring will not execute in Laravel. For pure-PHP helpers, vendor the source or copy isolated functions into your app and write your own tests. Avoid pulling it into CI until license and release facts are clear.