- Is ops-talent/apibundle a Laravel package?
- No. Despite being described as a Laravel API bundle, the repository is a Symfony bundle: it uses the Bundle suffix, DependencyInjection and Configuration conventions, and Symfony-style service registration. It will not register with Laravel's service container or expose Laravel-style configuration. If your application is Laravel, this package is a framework mismatch and effectively a non-starter.
- Can I install ops-talent/apibundle in a Laravel application with Composer?
- Composer may resolve it, but the code will not bootstrap in a Laravel app because Laravel does not auto-discover or register Symfony bundles. You would get no routes, no container wiring, and no working OAuth2 integration. There is no published evidence of any project using it outside Symfony 3.x/4.x.
- Which Laravel versions does ops-talent/apibundle support?
- None. There is no Laravel support matrix and no Laravel service provider in the package. The most recent release is July 2019, which places its Composer constraints in the Symfony 3.4/4.x and PHP 7.x era. Expect conflicts on any modern Laravel or PHP 8.x runtime.
- What does ops-talent/apibundle actually do?
- It is a thin opinionated wrapper for Symfony that adds RESTful controller conventions plus OAuth2 wiring, likely on top of FOSRestBundle and an older OAuth2 server library. Its goal was to reduce boilerplate when standing up consistent JSON API endpoints. In modern ecosystems that role is filled by API Platform on Symfony and by Sanctum or Passport on Laravel.
- Is ops-talent/apibundle still maintained?
- No. The last release was July 2019, the repository has a single star and zero dependents, and there is no visible maintainer activity or security disclosure channel. An unmaintained package that handles OAuth2 token flow is a security concern, not just a maintenance annoyance. Assume no fixes will arrive for new CVEs or runtime changes.
- What should I use instead of ops-talent/apibundle for OAuth2 in Laravel?
- Use Laravel Sanctum for first-party SPA and mobile token auth, or Laravel Passport for full OAuth2 server capabilities. Both are first-party, actively maintained, and integrate natively with Laravel's container, middleware, and guards. On modern Symfony, API Platform plus league/oauth2-server covers the same ground with current releases.
- Does ops-talent/apibundle work with PHP 8 or Symfony 5 and above?
- There is no published compatibility evidence for PHP 8.x or Symfony 5, 6, or 7. Given the 2019 release date, expect Composer conflicts on the upstream dependencies as well, since FOSRestBundle and older OAuth2 server implementations have been deprecated or replaced. Verify constraints with a Composer dry-run before writing any code.
- How do I check whether ops-talent/apibundle is compatible with my stack before installing?
- Run a Composer require with --dry-run against a scratch copy of your project to see whether the dependency graph resolves. Then confirm the bundle's Symfony version and OAuth2 library constraints against your target PHP and framework versions. With zero dependents, there is no field validation to lean on, so treat any successful resolution as unproven.
- What are the security risks of using ops-talent/apibundle in production?
- The core value of the package is OAuth2, which is security-critical code frozen since 2019. Risks include unpatched transitive dependencies with known CVEs, no disclosure or triage process, and drift from current best practice on token lifetimes, PKCE, and refresh token rotation. With one star and zero dependents, latent vulnerabilities are unlikely to have been found or reported.
- How would I migrate away from ops-talent/apibundle if it is already in production?
- Inventory what the bundle does in that codebase: route conventions, serializer configuration, and the OAuth2 server adapter. Replace each concern with a maintained equivalent, such as Sanctum or Passport on Laravel, or API Platform and league/oauth2-server on Symfony. Keep the external API contract stable so clients are unaffected by the swap. For greenfield work, skip the bundle entirely and start with a maintained library.