Weave Code
Http Laravel Package
slick/http
Slick HTTP is a lightweight HTTP package for PHP, offering a clean API for building requests and handling responses. It integrates easily into Laravel or standalone projects and keeps external API calls simple, testable, and maintainable.
slick/http is a lightweight HTTP layer for PHP that offers a clean, expressive interface for constructing and consuming HTTP requests and responses. It wraps common concerns—methods, headers, query parameters, and payloads—behind a fluent API, letting you focus on application logic instead of repetitive boilerplate.
- Fluent request builder for GET, POST, PUT, PATCH, and DELETE
- Immutable request and response objects
- Straightforward header, query, and body handling
- Framework-agnostic design with optional Laravel integration
- Minimal dependencies for fast, predictable behavior
Frequently asked questions about Http
- What is slick/http used for?
- slick/http provides PSR-7 HTTP message objects, a middleware-driven request runner, session handling, and an HTTP client for PHP. It is framework-agnostic and is not built around Laravel's HTTP kernel. Laravel developers should treat it as a standalone PSR-7/PSR-18 component, not as a replacement for Laravel's request lifecycle.
- Does slick/http work with Laravel?
- It can be installed in a Laravel project with Composer, but there is no Laravel service provider, facade, published config, or HttpFoundation bridge. Any integration is manual wiring rather than a first-party Laravel package experience. Full adoption would mean bypassing Laravel's kernel, routing, dependency injection, authentication, validation, and session management.
- How do I install slick/http in a Laravel project?
- Install it with Composer using composer require slick/http, then instantiate its classes directly in your code. There is no artisan vendor:publish step and no container bindings to register. Before committing, verify PHP version support, PSR-7 version constraints, and whether the client meets your PSR-18 needs.
- Is slick/http PSR-7 compliant?
- The package describes itself as a PSR-7 implementation, but conformance should be proven rather than assumed. PSR-7 has many edge cases around header normalization, stream seekability, file uploads, and immutability. Run the php-http/psr7-integration-tests suite before relying on it for interoperability.
- Does slick/http provide a PSR-18 HTTP client?
- The package overview states that it implements PSR-18, so it is intended for standardized HTTP client usage. You should still confirm whether it uses PSR-17 request factories or a bespoke wrapper and how errors and timeouts are handled. For Laravel apps, the built-in Http facade already covers retries, fakes, and testing assertions.
- Is slick/http middleware PSR-15 compatible?
- slick/http includes a middleware-driven request runner, but its middleware contract may be Slick-specific rather than PSR-15 compliant. If it is proprietary, you cannot reuse the wider PSR-15 middleware ecosystem. Verify the interface signature before designing around it.
- Can I use slick/http sessions in Laravel?
- Using slick/http sessions alongside Laravel is not recommended because it directly overlaps with Laravel's SessionManager, cookie encryption, CSRF protection, and driver abstraction. Running two session systems in one application is a defect generator. Use Laravel's session handling for Laravel apps and keep slick/http out of that layer.
- What are alternatives to slick/http for PSR-7 in Laravel?
- For PSR-7 messages, nyholm/psr7 and guzzlehttp/psr7 are the more common ecosystem choices. Laravel already converts between HttpFoundation and PSR-7 through symfony/psr-http-message-bridge. For HTTP clients, Laravel's Http facade is usually the better fit than adding a separate PSR-18 client.
- Is slick/http actively maintained?
- The available assessment notes zero stars, zero dependents, and a single recent release dated 2025-12-22. That shows the repository is alive but does not prove a maintainer team, security policy, or release cadence. Bus factor is high, so issues you file may go unanswered.
- Is slick/http safe for production Laravel applications?
- Full adoption in a Laravel production app carries high risk because it competes with Laravel's kernel, sessions, and HTTP client while having low adoption and limited maintenance signals. The most defensible use is isolated PSR-7 message handling inside a self-contained package that must avoid Laravel and Guzzle. For anything security-sensitive or long-lived, prefer audited alternatives and run conformance and security reviews first.
Weaver
How can I help you explore Laravel packages today?