Weave Code
Login Bundle Laravel Package
forci/login-bundle
ForciLoginBundle is a Symfony bundle that adds login and authentication handling to your application, packaging the configuration, routes, and services needed to wire up a sign-in flow with minimal setup. Part of the Forci package family.
At a glance
Frequently asked questions about Login Bundle
- Can I install forci/login-bundle in a Laravel app with Composer?
- You can run composer require, but it is not a supported integration. ForciLoginBundle is a Symfony bundle built on Symfony Security, and it ships no Illuminate service provider, package-discovery entry, publishable config, migrations, or Laravel auth guard driver. The likely result is Symfony security packages inside a Laravel tree with no working login flow. Treat it as a disposable spike at most, not a production dependency.
- Does ForciLoginBundle support Laravel 10 or Laravel 11?
- No. There is no Laravel support path in the artifact: no Illuminate Support ServiceProvider, no package discovery, and no integration with Laravel's AuthManager. Laravel's auth guards and Symfony's Security firewalls are parallel abstractions with different session, CSRF, and event semantics. Bridging them is adapter engineering, not configuration, and the package has no evidence of anyone doing it in production.
- What Laravel package should I use instead of forci/login-bundle?
- For standard login, two-factor authentication, and login throttling, use Laravel Fortify. For OAuth providers use Laravel Socialite; for API tokens use Sanctum or Passport; for federated identity use a vetted OIDC client. These are first-party or widely reviewed options with upstream support and idioms any Laravel engineer can maintain. That matters more for your bus factor than any feature delta from a small Symfony bundle.
- What is the license for forci/login-bundle?
- GitHub reports NOASSERTION, meaning it could not map the repository to a recognized SPDX identifier. Until the verbatim license and copyright holder are confirmed in writing, you have no clear grant to embed, redistribute, or reuse the code. That blocks engineering spend as well as release, not just legal review at the end.
- Is forci/login-bundle maintained and production-ready?
- There is no meaningful adoption signal: roughly 1 star, 0 dependents, and a composite score around 0.005. There are no known production users, no downstream compatibility testing, and no community triage to learn from. The context also shows no evidence of tests, CI, or recent commits. For an authentication component, that is not a production-ready risk profile.
- What features does ForciLoginBundle actually provide?
- The overview describes a lightweight Symfony bundle that wires Symfony Security into a ready-to-use login flow: configurable login routes, form handling, post-login redirects, and customizable templates. It does not establish SSO, SAML, OIDC, magic links, or throttling in the provided material. Before any evaluation, confirm whether the capability you need is generic form login or federated identity, because that changes the alternative by an order of magnitude.
- How do I install and configure forci/login-bundle in Symfony?
- The package is intended for Symfony: install via Composer and register the bundle in your kernel, then wire your user provider and firewall to the login routes it exposes. The overview advertises simple setup through Composer and bundle registration, with configurable routes, redirects, and templates. The exact commands and configuration keys are not in the provided README excerpt, so verify them against the repository before relying on them. You will also need to confirm PHP and Symfony constraint compatibility.
- Can I run ForciLoginBundle as a standalone identity service for Laravel?
- That is the isolation option: run it as a standalone Symfony identity broker exposing OIDC or SAML to Laravel. It is only warranted if the bundle encapsulates protocol logic you could not rebuild in materially less time. The cost includes a second runtime, session and CSRF reconciliation, operational ownership, and a security review of the auth flow. For generic form login, rebuilding natively in Laravel is cheaper and safer.
- What PHP and Symfony versions does forci/login-bundle require?
- The declared PHP and Symfony constraint ranges are not established in the provided material, and the transitive dependency graph appears uninspected and likely Doctrine-adjacent. That matters because an auth package with unknown constraints can silently pin or conflict with framework versions in your application. Before any trial, read composer.json, run a full dependency audit, and pin an exact commit if you proceed at all.
- How should I security-review or test ForciLoginBundle's auth flow?
- Assume you own the review: there is no evidence of tests or CI in the package, so build a harness around login, logout, redirect handling, and session behavior. Review token handling, session fixation, replay, CSRF, and remember-me semantics specifically. Also inventory the vendor namespace and transitive dependencies, because a low-traffic package will not surface in advisory feeds or SCA tooling keyed to known packages. Auth defects here resolve to tenant-wide lockout or auth bypass, so treat it as Tier-0.
Weaver
How can I help you explore Laravel packages today?