clue/socks-react
Async SOCKS4/4a/5 proxy connector for ReactPHP. Route TCP connections through a SOCKS server with non-blocking I/O, supporting authentication and DNS resolving via the proxy. Integrates with React\Socket to proxy outgoing connections.
Architecture fit: Requires ReactPHP event loop; incompatible with standard Laravel's synchronous HTTP stack. Only viable in async components (e.g., CLI tools, background workers).
Integration feasibility: Limited to ReactPHP-based parts of the system. Not compatible with Laravel's default request handling; would require significant refactoring for web requests.
Technical risk: Low maintenance (last release 2022), potential security vulnerabilities, compatibility issues with newer PHP/ReactPHP versions. Low community adoption (117 stars) suggests limited support.
Key questions: How will the ReactPHP event loop be managed alongside Laravel's synchronous processes? What is the plan for maintaining this dependency if it's inactive? Are there alternative maintained packages for SOCKS proxying in PHP?
Stack fit: Only suitable for non-web components (e.g., CLI tools, event-driven microservices). Not compatible with standard Laravel web applications.
Migration path: Start with a small CLI tool using ReactPHP; gradually expand to async workers. Requires decoupling from Laravel's HTTP kernel.
Compatibility: Requires ReactPHP components; may conflict with Laravel's default synchronous libraries (e.g., Guzzle). Needs separate event loop management.
Sequencing: 1) Evaluate need for async proxying in specific tasks. 2) Implement in isolated CLI/command context. 3) Test performance and stability. 4)
How can I help you explore Laravel packages today?