Weave Code
Latch Bundle Laravel Package
fourcoders/latch-bundle
Fourcoders LatchBundle integrates Telefónica Latch into Symfony apps, adding account lock/unlock and second-factor protection. Configure API credentials, pair user accounts, and query Latch status through simple bundle services.
Easy integration of Latch in your symfony2 project.
Frequently asked questions about Latch Bundle
- Is fourcoders/latch-bundle compatible with Laravel?
- No. fourcoders/latch-bundle is a Symfony 2 bundle built around Symfony DependencyInjection extensions and bundle service definitions, and Laravel has no bundle concept. Installing it in a Laravel app is not a supported or viable path.
- Can I install fourcoders/latch-bundle in Laravel 10 or 11 with Composer?
- No, Composer installation into a Laravel 10/11 app is not viable. The bundle requires Symfony 2.x components such as symfony/framework-bundle and symfony/dependency-injection 2.1–2.8, which conflict with the Symfony 5/6/7 components Laravel already depends on. You should expect a hard dependency-resolution failure, not a runtime bug you can patch around.
- What is Latch and is the Latch API still available?
- Latch was Telefónica ElevenPaths' account-lock and out-of-band approval service. It has been discontinued, so the latch.elevenpaths.com API endpoint no longer answers. Any integration built on Latch is dead on arrival regardless of the client code.
- What does fourcoders/latch-bundle actually do?
- It is a thin Symfony bundle that wraps the Latch REST API. It provides DI-configured services for pairing and unpairing accounts, querying Latch status, and locking or unlocking protected accounts. The functional surface is roughly 100–200 lines of code around an HTTP client plus possible route-level enforcement.
- Is fourcoders/latch-bundle actively maintained?
- No. The repository shows no maintainer activity since 2015-01-15, with about 10 stars, zero dependents, no CI badge, and no test suite referenced. It is a single-commit-era, unmaintained integration shim.
- What license does fourcoders/latch-bundle use?
- The package is marked NOASSERTION and has no LICENSE file, which under default copyright means all rights reserved. You cannot copy, modify, or redistribute the bundle until the fourcoders authors grant terms. There is no maintainer activity to resolve that clarification.
- Can I port fourcoders/latch-bundle to Laravel?
- You could rewrite the idea trivially as a Laravel service provider, config file, Guzzle/Http client, and middleware, but there is nothing worth porting from the bundle itself. More importantly, the Latch service it targets is discontinued, so a direct port would fail at the network layer. Treat this as a product decision about Latch, not a package migration.
- What are Laravel alternatives to Latch for two-factor or step-up authentication?
- Use live, maintained options: TOTP with pragmarx/google2fa, WebAuthn with web-auth/webauthn-lib, Laravel Fortify's built-in two-factor authentication, or Sanctum/Passport for device trust. These cover step-up auth, account lockout, and device pairing without relying on a dead API. Choose based on whether you need mobile push approval, TOTP, or WebAuthn.
- Does fourcoders/latch-bundle work on PHP 8.1 or later?
- No, it is not suitable for PHP 8.1+. The code uses PHP 5.3/5.4 idioms such as PSR-0 autoloading, no scalar type hints, and old array syntax, and it will not survive PHP 8.1+ static analysis. Expect deprecations or fatal errors even before considering the dead Latch API.
- How would I implement Latch-style account lock and unlock in Laravel?
- Implement the idea idiomatically with a Laravel service provider, config/latch.php, an HTTP client using Guzzle or the Http facade, and middleware or a Form Request rule for enforcement. But do not target Latch; use a live approval or two-factor provider instead. The out-of-band approval requirement is well served by TOTP, WebAuthn, or Fortify 2FA.
Weaver
How can I help you explore Laravel packages today?