Weave Code
Cli Laravel Package
hoa/cli
Hoa\Cli is a PHP library for building command-line interfaces, offering abstractions for commands, arguments, options, input/output, and terminal interaction. It fits the modular Hoa ecosystem for structured CLI application development.
hoa/cli is a lightweight PHP library from the Hoa project for building command-line interfaces. It provides reusable abstractions for defining commands, handling terminal input, and managing console output, helping developers create maintainable CLI tools without a heavy framework.
- Define and organize commands with clear entry points.
- Handle arguments and options from the terminal.
- Manage input/output for consistent CLI feedback.
- Integrate modularly with other Hoa components.
Frequently asked questions about Cli
- Is hoa/cli still maintained?
- No. The Hoa project is archived and read-only, and hoa/cli is more than eight years past its last release. There is no active maintainer, security response process, or CVE monitoring. Treat it as reference reading rather than a dependency.
- Does hoa/cli work with Laravel 10, 11, or 12?
- There is no Laravel integration surface: no service provider, no config publish, no facade, and no contract. Any use requires hand-rolled wiring in AppServiceProvider, and the package still registers global state on boot. Modern Laravel requires PHP 8.1+, while hoa/cli carries PHP 5.5/7.x-era constraints, so Composer resolution may fail or require --ignore-platform-reqs.
- How do I install hoa/cli with Composer?
- You can try composer require hoa/cli, but expect platform-constraint failures on modern PHP. Succeeding only with --ignore-platform-reqs is a red flag, not a workaround. The recommended approach is not to install it in a Laravel application.
- Can I use hoa/cli instead of Artisan or Symfony Console?
- Practically, no. Its functionality overlaps almost entirely with Artisan and Symfony Console helpers, plus laravel/prompts for interactive input, validation, and styled output. Hoa\Cli sits beside Laravel's console layer rather than on top of it, so you would maintain two input/output abstractions in one process. Implement missing capabilities directly against platform primitives.
- What PHP versions does hoa/cli support?
- The evaluation indicates PHP 5.5/7.x-era constraints, but PHP 8 compatibility is unverified and unlikely. Hoa code predates PHP 8's reserved-word and signature strictness, so expect deprecations and possible fatals. Test with E_ALL and deprecations as errors before considering any spike.
- Is hoa/cli safe for production?
- No, the technical verdict is reject as a production dependency. Abandonment risk is certain, with no patch path, and any vulnerability becomes yours to fork. It also registers a custom hoa:// protocol and stream-wrapper layer via bootstrap side effects, creating ambient runtime and autoload risk.
- Does hoa/cli support --no-interaction and CI pipelines?
- It is unlikely to honour Laravel's --no-interaction flag because the library predates and has no knowledge of it. Readline-style helpers that block on STDIN can hang pipelines unless every call site is guarded. Confirm TTY detection and STDOUT/STDERR separation under your CI runner before any spike.
- What are the best alternatives to hoa/cli in Laravel?
- Use the idiomatic Laravel stack: laravel/prompts for interactive input, symfony/console helpers such as Table, ProgressBar, and QuestionHelper for structure, and nunomaduro/termwind for styled output. Artisan already provides these primitives. There is no identified gap that justifies adding hoa/cli.
- Why does hoa/cli conflict with Composer autoloading?
- Hoa packages are not self-contained; they assume hoa/consistency and hoa/stream, which register a custom hoa:// protocol and stream-wrapper layer via a bootstrap side effect. This ambient dependency is a known source of conflicts with Composer's PSR-4 autoloader and other packages that touch stream wrappers. It is also hard to attribute during incident response.
- Should I fork or vendor hoa/cli?
- Only if a one-day, timeboxed spike proves a specific missing capability and you assign an owner and maintenance budget. Even then, isolate it behind a single adapter class on a throwaway branch. The default recommendation is no migration: do not introduce the dependency, and implement directly against platform primitives.
Weaver
How can I help you explore Laravel packages today?