Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Cf Request Laravel Package

pdphilip/cf-request

cf-request is a Laravel package for accessing Cloudflare request data. It exposes headers like the connecting IP, visitor country, Ray ID, and other Cloudflare metadata, making edge information easy to use without manual header parsing.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Confirms the package is viable for roadmap work targeting Laravel 11, 12, or 13; Laravel 13 support lets teams standardize on current framework versions without maintaining a fork.
  • Supports build-vs-buy decisions for Cloudflare API integration: use the package for common Cloudflare request/response flows instead of maintaining a custom HTTP client wrapper.
  • Informs upgrade planning: v3.1.0 drops Laravel 10 (EOL), so products still on Laravel 10 must either pin to v3.0.x or schedule a framework upgrade before adopting this release.
  • Improves confidence in maintenance hygiene: CI now covers PHP 8.3/8.4 and Laravel 11/12/13, with per-version Composer test scripts and a Laravel HTTP client fix for Larastan 3.
  • Relevant use cases include Cloudflare-backed admin dashboards, cache purge automation, DNS/zone operations, and other workflows that depend on Cloudflare API requests from a Laravel application.

When to Consider This Package

  • Consider it when your application runs Laravel 11, 12, or 13 on PHP 8.3/8.4 and you need a maintained Laravel-native wrapper for Cloudflare API requests.
  • Good fit if you want to avoid building and maintaining your own Cloudflare HTTP client, authentication handling, and response parsing.
  • Re-evaluate if you are on Laravel 10: v3.1.0 is not compatible. Pin to v3.0.1 only as a short-term bridge, and plan the Laravel upgrade first.
  • Look elsewhere if you need an official Cloudflare SDK, multi-language support, or capabilities outside this package’s request-wrapper scope.
  • Also look elsewhere if adding pdphilip/omniterm as a dependency conflicts with your dependency policy, or if you require a release with new product features rather than compatibility and maintenance updates.
  • This release is primarily a compatibility/maintenance release, not a feature expansion; do not adopt it solely expecting new product capabilities.

How to Pitch It (Stakeholders)

  • Executives: “This package gives us a maintained, low-cost way to integrate Cloudflare operations into our Laravel product and keeps us aligned with supported Laravel versions. The new release supports Laravel 13 and drops only end-of-life Laravel 10, reducing long-term maintenance risk.”
  • Engineering: “v3.1.0 is a compatibility release: Laravel 11/12/13 support, PHP 8.3/8.4 CI, per-version test scripts, and a Laravel HTTP client fix for Larastan 3. No new product features. The main impact is the Laravel 10 drop, so treat it as a breaking change for any L10 service.”
  • Product: “Use it where we need Cloudflare-backed admin or automation workflows and want to avoid custom API plumbing. If any service is still on Laravel 10, budget the framework upgrade before rolling this release out.”
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
socialdept/tenant-domains
tautvydasr/blade-class-names
socialdept/color-scales
maherelgamil/controller
coleus/widgets
coleus/table
coleus/users
coleus/music
coleus/health
coleus/calendar
coleus/notes
coleus/support
coleus/settings
coleus/apps
seampact/laravel
emmyconceptng/laravel-ng-postcode
jjsquady/round-robin
skyraptor/chatter
edlugz/sasapay
abbasudo/artisan-route