- Is baks-dev/users-profile-balance a Laravel package?
- No. It is a Symfony bundle built around Symfony Console and Doctrine ORM, so it is not a drop-in for Laravel. The install steps use php bin/console and doctrine:migrations commands, which do not exist in a standard Laravel app. Treat any Laravel-native description as incorrect unless an adapter or port is built.
- Can I install baks-dev/users-profile-balance in a Laravel application with Composer?
- Composer may resolve the package, but installation alone does not make it usable in Laravel. You would still need a Doctrine bridge, an adapter layer, or a fork-and-port of the MIT source. That is a build project, not a normal Laravel package install.
- What PHP version does baks-dev/users-profile-balance require?
- The package requires PHP 8.4 or newer. That floor can constrain hosting, CI images, and upgrade paths if the host application is still on an older PHP version. Verify runtime parity before committing.
- How do I install and configure baks-dev/users-profile-balance in Symfony?
- Run composer require baks-dev/users-profile-balance, register the bundle, and run php bin/console baks:assets:install. Then generate and review a Doctrine migration with doctrine:migrations:diff and apply it with doctrine:migrations:migrate. The README also suggests auto-scripts for post-install and post-update, which should be reconciled with your existing pipeline.
- How do I run the package tests for users-profile-balance?
- The README documents php bin/phpunit --group=users-profile-balance. That assumes a Symfony/PHPUnit setup with the package installed and test configuration available. In a Laravel app, the same command is not applicable without porting the test harness.
- Does baks-dev/users-profile-balance support loyalty tiers, multi-currency, expiry, or payment gateways?
- No, not according to the README. The documented scope is a profile-scoped balance with persistence and a service API, plus installation and testing steps. Claims about loyalty tiers, multi-currency, expiry, fraud checks, or payment gateways are speculative unless you find them in the source.
- Is balance mutation atomic and safe against concurrent debits or double-spend?
- The README does not document transactions, row locking, optimistic versioning, or idempotency. Concurrent debits and double-spend behavior are therefore undocumented correctness risks. You must inspect the source and add locking or a ledger design before handling real money.
- Does the package keep an audit trail or transaction history?
- The documented model is a numeric balance attached to a profile, which suggests a mutable current-value column. No immutable transaction or audit ledger is documented. Reconstructing why a user has a specific balance would require additional history you build yourself.
- Can a user have multiple balances, such as points and credits, with this package?
- The README describes a profile-scoped balance, not a ledger or multi-account wallet. It does not document multiple balance types per profile or separate point and credit accounts. If you need those primitives, plan to extend or fork the model.
- Is baks-dev/users-profile-balance production-ready and actively maintained?
- There is little public adoption evidence, including zero stars and zero dependents at assessment time, and release notes lack changelog discipline. The package is MIT licensed with no hidden dependencies observed, but it has a single-maintainer bus factor. Pin versions, diff patch releases, audit composer.lock, and keep a fork-and-own contingency.