Weave Code
Slack Laravel Package
quitoque/slack
A Laravel package for integrating Slack into your application, making it easy to send messages and notifications to Slack channels through a simple, configurable API.
Access your Slack Team's API through PHP objects
Frequently asked questions about Slack
- How do I install quitoque/slack in a Laravel application?
- Install it with Composer using composer require quitoque/slack. Then register the package service provider if your Laravel version does not auto-discover it, and publish any configuration file the package provides so you can add Slack credentials. Before installing, check the composer.json constraints for PHP, Illuminate, and Guzzle versions to confirm it fits your current stack.
- Does quitoque/slack support Laravel 10 or Laravel 11?
- Laravel version support is not confirmed by the available package signals, so you must inspect its composer.json for Illuminate constraints. The package appears small and low-traffic, which makes it likely to lag behind current Laravel majors. Run a one-day install spike on your exact Laravel and PHP versions before committing engineering time.
- Which Slack authentication method does quitoque/slack use: webhook, bot token, or legacy token?
- The available context does not confirm the authentication model, and this is the key gating question. Slack retired legacy tokens in 2020 and moved to OAuth v2 scopes and bot tokens, so a package published years ago may target deprecated auth. If it does not support incoming webhooks or bot tokens, treat it as disqualified for new integrations.
- Is quitoque/slack safe to use in production?
- The technical risk is high: the package has zero stars, zero dependents, no visible CI, and single-organization provenance. It also holds Slack tokens and makes outbound HTTP calls, so unmaintained dependencies and API drift are real supply-chain and reliability concerns. For production, prefer Laravel's official Slack notification channel or a small internal client you control.
- How do I send a Slack message with quitoque/slack?
- The package is intended to expose Slack's Team API through PHP objects, presumably with a Laravel service provider and injectable client. After installing and configuring credentials, you would resolve the bound client or facade and call its messaging methods from your application. The exact method names are not documented in the provided context, so verify them against the package source during your spike.
- Can quitoque/slack send Laravel notifications to Slack channels?
- It can send messages to Slack, but it is not the same as Laravel's native notification integration. Laravel ships laravel/slack-notification-channel with Notifiable, toSlack(), and Block Kit support, which is better suited to notification workflows. Use quitoque/slack only if it exposes a specific Slack API capability the official channel does not cover.
- What are the best alternatives to quitoque/slack for Laravel Slack integration?
- The first alternatives are Laravel's official laravel/slack-notification-channel for notifications and Spatie's laravel-slack-alerts for alerting use cases. For simple messaging, a thin Guzzle HTTP client or incoming webhook call is often cheaper to own than an opaque third-party wrapper. If you need a broader API wrapper, verify maintenance and Slack API currency before adopting one.
- Does quitoque/slack handle Slack rate limits and API errors?
- There is no evidence of robust handling for Slack's tiered rate limits, ok:false response envelopes, or Retry-After headers. Object-oriented wrappers often abstract over these error semantics, which is exactly where Slack integrations break in production. You should inspect the source and add your own retry, logging, and failure handling before relying on it.
- Is quitoque/slack actively maintained, and how do I report bugs?
- Maintenance signals are weak: zero stars, zero dependents, no visible CI, no releases narrative, and no contributor community. The publisher is a commercial meal-kit operator, not a library vendor, so bug reports route to an organization with little incentive to service external users. Treat it as an internal integration extracted for convenience rather than a maintained open-source product.
- Can I fork quitoque/slack if it is unmaintained?
- Forking may be viable if the license and provenance allow it, so check the repository license and whether the code derives from a known upstream such as a maknz/slack lineage. If you fork, internalize the code, pin dependencies, and add tests that mock Slack HTTP responses. In many cases, replacing it with a 100-line internal Slack client is cheaper than maintaining an opaque package.
Weaver
How can I help you explore Laravel packages today?