- What is fi/fifreecorebundle and what does it actually do?
- FiFreeCoreBundle is a lightweight foundational core bundle that collects shared utilities, base services, and configuration defaults that most PHP projects end up rewriting. It is published under the fi vendor prefix by Comune di Firenze and is intended as a consistent starting point so teams can focus on feature work instead of boilerplate. It ships reusable base services, overridable defaults, and simple integration hooks with minimal dependencies. Note that the repository evidence points to a Symfony bundle rather than a Laravel package.
- Is fi/fifreecorebundle a Laravel package or a Symfony bundle?
- The evidence points to a Symfony bundle: the fi vendor prefix, the Bundle suffix, a FifreeCoreBundle class extending Symfony's Bundle, and no Illuminate or service-provider artifacts. The brief calls it a Laravel/PHP package, but that premise should be corrected before any roadmap commits to it. Treating it as a Laravel package will likely burn a sprint on a failed composer require. Verify this yourself from composer.json and the bundle class before planning anything.
- Can I install fi/fifreecorebundle directly into a Laravel application?
- Direct installation into an existing Laravel app is effectively out of scope until a spike proves otherwise. The bundle is opinionated at the kernel, container, and configuration-tree seam, which is exactly the surface Laravel does not expose, and there is no bridge package or dependents to copy patterns from. Feasible paths are extracting domain classes behind your own interfaces, forking and wrapping in an adapter, or running Symfony alongside Laravel for one bounded context. Do not fund a make-it-work-in-Laravel effort unless you accept it is an architecture project.
- How do I install fi/fifreecorebundle with Composer?
- The conventional command is composer require fi/fifreecorebundle, but there is no observable tagged release cadence in the metadata, so you may need to pin a commit SHA via a VCS repository entry. Before running anything, read LICENSE and composer.json to confirm the license and the declared PHP and Symfony version constraints. Run the first install in a disposable container, not in an application you care about.
- Which PHP, Symfony, or Laravel versions does fi/fifreecorebundle support?
- There is no published version matrix, so the only reliable source is the require block in composer.json. Expect constraints tied to whatever Symfony and PHP versions the parent Fifree framework targeted. Laravel version support is not declared at all, which is consistent with it not being a Laravel package. Test against your target runtime in an isolated container before assuming compatibility.
- How do I override the default configuration in fi/fifreecorebundle?
- The bundle ships sensible configuration defaults designed to be overridden, which in Symfony means the usual config tree loaded through config/packages YAML files. Because Laravel uses config/*.php arrays and a different configuration repository, you would have to map those defaults yourself if you attempt any port. Keep your overrides in your own namespace so upstream changes do not silently take precedence.
- Does fi/fifreecorebundle have tests, CI, or a security disclosure channel?
- The available metadata shows no observable release cadence, CI pipeline, test suite, or security-disclosure channel. That absence is a supportability risk rather than a code-quality judgement. An unpatched core package sitting under an application becomes a permanent CVE-absorption liability, so identify a named owner at ComuneFI before depending on it. Also check whether the test suite can run without municipal infrastructure.
- What license does fi/fifreecorebundle use, and can I use it in a commercial SaaS product?
- Licensing is ambiguous from the metadata alone, and Italian public administrations commonly publish under EUPL or, riskier for SaaS, AGPL. An AGPL finding can cancel a commercial roadmap item on day one, so confirm the license from LICENSE and composer.json before scoping anything downstream. Document the redistribution and SaaS obligations you conclude, and have legal sign off before adoption.
- Is fi/fifreecorebundle production-ready and actively maintained?
- Ecosystem signal is effectively zero: no stars, no dependents, no public API-stability contract, no peer users, and no Stack Overflow corpus to lean on. The opportunity score signals latent domain value, not adoption readiness. Its durable value is likely domain encoding for Italian public administration such as SPID and CIE identity, ANPR registry, PagoPA payments, and protocollo, rather than infrastructure. Also expect Italian-only documentation and public-sector vocabulary with no English onboarding path.
- What is the realistic way to reuse fi/fifreecorebundle in a Laravel project, and what are the alternatives?
- Prefer extraction over adoption: audit the capability inventory from LICENSE, composer.json, README and tests, run a one-sprint spike in a disposable Symfony container to exercise the two or three capabilities you actually need, then port the domain logic into your own namespace behind interfaces you own with upstream attribution preserved. For a genuine Laravel foundation, consider the Laravel skeleton, first-party service providers, or a package like spatie/laravel-package-tools instead. For Italian public-sector domain patterns, mine the design rather than taking a dependency on the artifact. If you only need shared utilities, a small in-house core package will usually cost less than the integration risk here.