- Is orukusaki/slackbundle a Laravel package?
- No. orukusaki/slackbundle is a Symfony2 bundle, so it depends on the Symfony kernel, dependency injection container, and event dispatcher lifecycle that Laravel does not implement. It ships no Laravel service provider, facade, or configuration publishing convention. Using it in Laravel means ignoring the bundle wiring entirely and manually reusing whatever framework-agnostic Slack client code sits underneath.
- Can I install orukusaki/slackbundle in a Laravel 10 or Laravel 11 application?
- Technically you can attempt a Composer install, but the practical value is low and compatibility is unverified. The bundle targets Symfony2 and likely declares a PHP constraint that predates PHP 8.x, so it may not resolve cleanly alongside modern Laravel dependencies. Run a composer require spike in a throwaway branch before scheduling any real integration work.
- How do I install orukusaki/slackbundle with Composer?
- The normal install is composer require orukusaki/slackbundle, followed by registering the bundle in a Symfony AppKernel. In Laravel there is no bundle registration step, so you would have to instantiate the underlying client manually in a service provider. Check the package's composer.json PHP constraint first, because stale metadata can block installation on current runtimes.
- What should I use instead of orukusaki/slackbundle for Slack notifications in Laravel?
- Use Laravel's native Slack notification channel via laravel/slack-notification-channel for standard messaging. It provides idiomatic configuration, notification testing fakes, and active maintenance. For interactive Slack apps such as slash commands, Events API subscriptions, or OAuth install flows, consider the community-maintained SlackPhp SDK or a small in-house client.
- Does orukusaki/slackbundle work with the current Slack Web API?
- That is unverified. The bundle predates major Slack changes including granular OAuth scopes, Events API v2, updated chat.postMessage payloads, and the deprecation of legacy token types. Without an active test suite or recent releases, any hardcoded endpoint or payload shape in the package should be treated as suspect until you run a spike.
- What PHP versions does orukusaki/slackbundle support?
- The package targets Symfony2, so its PHP constraint most likely predates PHP 8.x and its Composer metadata may be stale. Do not assume it installs on modern PHP without verifying the constraint in composer.json. A quick install test on your target runtime is the fastest way to confirm.
- How do I send a Slack message from Laravel without this bundle?
- For simple messaging, post to an incoming webhook with Laravel's HTTP client, or use the native Slack notification channel. Both approaches take only a few lines and avoid legacy Symfony dependencies. If you need more control, wrap the Slack Web API in a small App\Services\SlackClient class that your application owns.
- Is orukusaki/slackbundle actively maintained?
- The evidence points to no. It has roughly 10 stars, a Symfony2 target, and no recent releases, which places it among unmaintained pre-Symfony 3 code. Any upstream fixes to its Symfony wiring would be irrelevant to a Laravel integration anyway. Treat it as abandoned when assessing total ownership cost.
- Can orukusaki/slackbundle handle Slack slash commands or the Events API?
- It is designed for simple Slack API messaging and incoming webhook notifications, not for modern interactive app flows. Slash commands, Events API v2 subscriptions, and OAuth installation flows require request signature verification and token handling the bundle does not provide. Use a maintained Slack SDK or a purpose-built in-house client for those use cases.
- What are the security risks of adding orukusaki/slackbundle to a production Laravel app?
- Installing it can pull legacy, likely end-of-life transitive dependencies into composer.lock, creating CVE and audit liability on a modern PHP runtime. The package itself is unmaintained, so any vulnerabilities in its code or dependencies are unlikely to be patched. Either avoid it in the production dependency graph or vendor and audit the small amount of client code you actually need.