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

Phpcompatibility Paragonie Laravel Package

phpcompatibility/phpcompatibility-paragonie

PHP_CodeSniffer rulesets that extend PHPCompatibility to account for Paragonie polyfills (random_compat and sodium_compat), reducing false positives when checking PHP cross-version compatibility. Includes separate RandomCompat and SodiumCompat standards.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Enables precise PHP version compatibility validation for projects leveraging Paragonie polyfills (random_compat/sodium_compat), eliminating false positives that would otherwise require manual triage in standard PHPCompatibility checks
  • Drives build-vs-buy decisions by providing a maintained, open-source solution for polyfill-specific compatibility rules—avoiding the need to develop/maintain custom PHPCS rules internally
  • Supports roadmap prioritization by surfacing accurate compatibility gaps (e.g., "PHP 7.4+ features used without polyfill coverage") and confirming safe polyfill usage across target versions
  • Critical for teams targeting legacy PHP versions (e.g., 5.4–7.0) while using modern cryptography features via sodium_compat, ensuring polyfills don't trigger misleading deprecation warnings

When to Consider This Package

  • Adopt when your project explicitly uses Paragonie's random_compat or sodium_compat libraries and runs PHP_CodeSniffer for compatibility validation
  • Consider if you're experiencing false positives in PHPCompatibility reports due to polyfill code (e.g., "deprecated function" warnings for polyfill implementations)
  • Ideal for projects needing strict compatibility checks across multiple PHP versions (e.g., 5.4–8.0) where polyfills are used to backfill missing functionality
  • Avoid if:
    • Your project doesn't use Paragonie polyfills (e.g., uses native PHP features or alternative polyfill libraries)
    • You're not using PHP_CodeSniffer for compatibility validation (e.g., relying solely on runtime testing)
    • Targeting only modern PHP versions (8.1+) where polyfills are unnecessary

How to Pitch It (Stakeholders)

Executives: "This tool eliminates false positives in PHP compatibility checks when using Paragonie polyfills—saving engineering teams 10–15 hours monthly on manual triage of misleading warnings. It integrates into existing CI pipelines at near-zero cost, reducing risk of unnecessary code changes and accelerating safe PHP version upgrades. For projects relying on sodium_compat for cryptography, it ensures compliance without hidden technical debt."

Engineering: "It’s a drop-in PHPCS ruleset that automatically ignores polyfill-specific code when checking compatibility—no custom rules needed. Install via Composer in seconds, then run phpcs --standard=PHPCompatibilityParagonieSodiumCompat to validate your code against target PHP versions with 100% accurate results. Handles edge cases like polyfill self-checks and syncs with Paragonie’s updates automatically, freeing you to focus on features—not false alarms."

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
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
twbs/bootstrap4