Weave Code
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

Humbug Get Contents Laravel Package

padraic/humbug_get_contents

Drop-in replacement for file_get_contents() that secures HTTPS requests on PHP 5.3+ by injecting a strict SSL/TLS stream context (CA validation, verification). Helps prevent MITM attacks when fetching APIs, PHARs, or other remote content.

View on GitHub
Deep Wiki
Context7

Technical Evaluation

Architecture fit: The package is a minimal wrapper designed exclusively for PHP 5.3–5.5 environments where native SSL/TLS verification is insecure by default. It has no relevance for modern PHP versions (7.4+) due to built-in secure defaults, making it redundant for new projects. Its architecture is fundamentally tied to legacy PHP stream context behavior, which is obsolete in current ecosystems.

Integration feasibility: Low. While Composer installation is straightforward, the package lacks compatibility testing for PHP 8.x and newer SSL standards. Its reliance on Composer’s CA bundle (which hasn’t been updated since 2018) creates immediate risks for modern certificate authorities. The archived status means no validation against current PHP runtime behaviors or security patches.

Technical risk: High. The package has not been maintained since 2018, leaving known vulnerabilities (e.g., HTTPoxy in 1.1.2) potentially unaddressed for newer attack vectors. Outdated CA bundles may cause SSL handshake failures with modern endpoints, and the absence of security updates makes it a liability for compliance-sensitive systems. Using it instead of maintained HTTP clients (e.g., Guzzle) introduces technical debt and increases exposure to undetected vulnerabilities.

Key questions:

  • Why not migrate to Guzzle or Symfony HttpClient for secure, actively maintained HTTP operations?
  • Is the project truly constrained to unsupported PHP 5.3–5.5? If so, prioritize PHP upgrade over relying on this package.
  • How will the team handle CA bundle updates or certificate validation failures given the package’s archived status?

Integration Approach

Stack fit: Only applicable for legacy PHP applications (5.3–5.5) with no other viable options for securing file_get_contents() calls. Incompatible with modern PHP stacks (7.4+), PSR-7/18 clients, or any environment requiring HTTP/2, streaming, or advanced HTTP features. Should never be used in new projects or micro

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.
davejamesmiller/laravel-breadcrumbs
artisanry/parsedown
christhompsontldr/phpsdk
enqueue/dsn
bunny/bunny
enqueue/test
enqueue/null
enqueue/amqp-tools
milesj/emojibase
bower-asset/punycode
bower-asset/inputmask
bower-asset/jquery
bower-asset/yii2-pjax
laravel/nova
spatie/laravel-mailcoach
spatie/laravel-superseeder
laravel/liferaft
nst/json-test-suite
danielmiessler/sec-lists
jackalope/jackalope-transport