Console Laravel Package

Product Decisions This Supports

• Build vs. buy for PHP CLI surface area. Hoa\Console covers the lower-level layer of terminal work — argument/input parsing, TTY detection, cursor and screen control, readline-style input, and child-process handling — so it informs whether you hand-roll terminal primitives, adopt a framework console component, or layer a library on top.
• Legacy dependency triage. With zero recorded dependents, an archived repository, and a last release in May 2017, the primary decision this supports is not "should we adopt" but "what do we do if it is already in our tree." That is a scoped migration/exit decision with a clear owner and a bounded timeline.
• Roadmap: feature feasibility for interactive CLIs. Useful as a capability reference when scoping interactive installers, setup wizards, REPL-like tooling, progress/ANSI output, or prompts that must behave correctly when piped vs. attached to a real terminal. It answers "is this hard?" — not "what do we ship on?"
• Competitive/architecture comparison. Serves as a comparison point against symfony/console, laravel/prompts, and ReactPHP-style async process libraries, giving engineering a concrete alternative to evaluate rather than an abstract debate.
• Standards and risk policy input. A clean example of why an "abandoned dependency" gate (archived repo, >24 months without release, no security response path) belongs in the intake checklist before any package reaches a roadmap commitment.

When to Consider This Package

Reasonable to consider only when:

• It is already a transitive or direct dependency and the goal is understanding behavior, pinning a version, or planning a like-for-like replacement.
• You need low-level terminal primitives (TTY/ANSI handling, cursor control, process execution) that higher-level console components abstract away, and you are evaluating options.
• The work is a short-lived internal script or throwaway tooling where maintenance horizon is measured in weeks and no user data or production surface is exposed.
• You want a reading reference for how to model terminal I/O in PHP before writing your own thin wrapper.

Look elsewhere when:

• The code is new production surface — an archived library with no maintainer, no security response channel, and a nine-year-old release cadence is a standing liability, not a foundation.
• You need modern PHP support (PHP 8.x typing, attributes, current deprecation compliance) or any guarantee of forward compatibility.
• Compliance or procurement review applies: archived status is typically a hard fail regardless of code quality.
• You need community support, documentation freshness, or hiring-pool familiarity — the practical on-ramp cost for a new engineer is high here.
• Higher-level alternatives cover the requirement: symfony/console for command structure and I/O, laravel/prompts for interactive UX in Laravel applications, clue/shell-react or react/child-process for async/interactive process work.

Treat the low opportunity signal (~22/100) alongside the archive status as corroborating, not independent, evidence: this is a reference artifact, not a candidate dependency.

How to Pitch It (Stakeholders)

For executives (30 seconds): A dependency review surfaced hoa/console, an archived PHP terminal library last released in 2017 with no dependents in our codebase and no active maintainer. Our recommendation is no new investment and no adoption. If it is already present anywhere, we cap exposure and schedule a replacement inside an existing maintenance window — this is a small, contained cleanup, not a program. Cost of action is measured in days; cost of inaction is an unpatched, unsupported component in our CLI tooling with no one to call when it breaks.

For engineering leads (one paragraph): hoa/console solves a real problem well for its era — terminal abstraction, argument handling, cursor/TTY control, process management — and that makes it genuinely useful as a design reference when we scope interactive CLI features. It is not a viable runtime dependency: the upstream project is archived, the release line stopped in 2017, there is no security response path, and it predates modern PHP. Where we need these capabilities, we standardize on symfony/console for command structure and laravel/prompts for interactive flows, and we scope low-level terminal work explicitly rather than inheriting it. Ask: confirm whether it appears anywhere in our dependency graph; if yes, we produce a one-page replacement plan with an owner and a date.