- Is terox/subscription-bundle a Laravel package?
- No. It is a Symfony bundle, and its last functional release was in 2018 targeting Symfony 3.3/4+. There is no Laravel service provider, facade, or config integration, so it cannot be dropped into a Laravel app like a native package.
- How do I install terox/subscription-bundle?
- Install via Composer with composer require terox/subscription-bundle, but expect compatibility issues. The package targets Symfony 3.3/4+ and has no confirmed support for PHP 8. The 0.2.0 release notes are silent on PHP and Symfony version support, so verify against your platform before committing.
- Does terox/subscription-bundle support Laravel 10 or 11?
- No. It is a Symfony bundle and does not provide Laravel integration. Laravel 10 and 11 require PHP 8.1+ and modern framework contracts that this package does not declare. There is no evidence of testing against any Laravel version.
- What PHP versions does terox/subscription-bundle support?
- The package has no explicit PHP version constraints in its 0.2.0 release notes. Given its 2018-era Symfony 3.3/4+ target, it is near-certainly incompatible with PHP 8. Treat PHP 7.x as the practical ceiling unless you fork and test.
- How do I define plans and check entitlements with terox/subscription-bundle?
- You define plans and subscriptions through the bundle's manager classes, then check active entitlements wherever access matters. The 0.2.0 release added an owner parameter to ManagerSubscription::create() and a UserInterface parameter to findByProduct(), so your user model must satisfy their contract. Expect to adapt call sites and write your own integration layer.
- What changed in terox/subscription-bundle 0.2.0?
- Version 0.2.0 added an owner parameter to ManagerSubscription::create(), a UserInterface parameter to findByProduct(), and a new findById() method. These are breaking changes to the most-used entry points with no deprecation cycle or migration guide. It also confirms that UserInterface is a compile-time dependency of the core API.
- Is terox/subscription-bundle safe for production billing?
- High risk. The package is money-adjacent, has no visible test suite, and its 0.2.0 release changed public signatures without platform compatibility notes. The schema is still in flux (an owner field was added mid-life), so any billing logic you build inherits an unsettled data model.
- What are alternatives to terox/subscription-bundle for Laravel?
- For Laravel, consider native packages like Laravel Cashier (Stripe/Paddle) or Laravel Spark for SaaS billing. For general PHP, look at Symfony-based subscription bundles with active maintenance or build a small domain model yourself. The terox bundle's 11 stars, 0 dependents, and 2018-era code make it a poor foundation.
- How do I test terox/subscription-bundle integration?
- There is no published test suite or CI status for the package, so you must write your own integration tests. Focus on the owner and ID lookup paths added in 0.2.0, since those are new and likely uncovered. Use a fork or wrapper to isolate the unstable API from your application code.
- Is terox/subscription-bundle maintained?
- It is not actively maintained in any reliable sense. After a multi-year silence, 0.2.0 landed as a one-off release with breaking changes and no deprecation path. One release after five years is a data point, not a maintenance commitment, and there is no one to escalate security issues to.