- Is nti/notification-bundle compatible with Laravel?
- There is no evidence in the provided release information that it is a Laravel package. It uses Symfony's Bundle naming convention, and v1.1.2 shows no Laravel service provider, config publishing, or facade. Treat it as Symfony-targeted until you verify composer.json and the source yourself.
- How do I install nti/notification-bundle?
- The Composer package name is nti/notification-bundle, so installation would normally start with composer require nti/notification-bundle. However, the package appears to target Symfony, and no Laravel auto-discovery or manual service-provider wiring is evidenced. Before installing, confirm the framework target, PHP version constraints, and whether Doctrine setup is required.
- Does it support Laravel 10, 11, or 12?
- Laravel 10, 11, and 12 compatibility is unverified in the provided assessment. There is no supported-versions matrix, and the release notes do not show bounded illuminate/* constraints. PHP 8.1 through 8.3 support is also unverified, so you would need to inspect composer.json and run a spike.
- What notification channels does NTI NotificationBundle support?
- The overview describes channel-based delivery across multiple transports, but it does not list concrete channels. The Guzzle dependency suggests the channel abstraction is HTTP-client-centric, likely for REST provider APIs, SMS gateways, push providers, or chat webhooks. It is less likely to be a general SMTP/mailer driver layer. The extensibility of the channel interface for non-HTTP transports is undocumented.
- Does NTI NotificationBundle require Doctrine?
- The overview states it provides Doctrine-backed notifications for storing and retrieving user alerts, so Doctrine is part of the intended persistence model. The provided information does not document the required Doctrine setup, mappings, or migrations. Plan for Doctrine configuration before using it in production.
- Is nti/notification-bundle abandoned or maintained?
- It is best described as minimally responsive at best, not fully dead. A v1.1.2 release exists after roughly four years of inactivity, but the visible change is a dependency-constraint update rather than evidence of ongoing feature maintenance. The package still shows 0 dependents, no changelog, no CI badge, no supported-versions matrix, and no documentation. A single dependency bump should not be treated as a security-response path.
- Are there tests or CI for nti/notification-bundle?
- No tests, CI badge, or visible test run are evidenced for the release. That matters because a dependency-constraint change can silently break HTTP-layer behavior such as timeouts, retries, and exception types. You should add your own integration tests around any channel you rely on.
- What is the risk of the Guzzle >=6.0 constraint?
- The documented constraint is >=6.0 with no upper bound, which admits Guzzle 7 today and any future major such as 8.x tomorrow. Guzzle 6 itself has been end-of-life since 2019. An unrelated composer update in a consuming service could pull a Guzzle major with breaking behavior or different TLS/proxy semantics than the package assumes. If you fork or adopt it, consider pinning ^7.0 after verifying compatibility.
- How does NTI NotificationBundle integrate with Symfony services and configuration?
- The overview says it integrates through Symfony services, events, and configuration. The release information does not include documentation for service IDs, event names, configuration keys, or bundle registration. You would need to inspect the bundle source and README to wire it correctly.
- What should Laravel developers use instead of nti/notification-bundle?
- Laravel developers should first evaluate Laravel's built-in notification system, which provides mail, database, broadcast, and other channels with framework-native service-provider integration. If you need a third-party package, prefer one with verified Laravel 10/11/12 support, bounded dependencies, tests, CI, and documented service-provider/config publishing. NTI NotificationBundle should be treated as a Symfony reference implementation unless a Laravel integration is proven. Avoid adopting it solely on the strength of the v1.1.2 dependency bump.