has

The tool inspects the system’s PATH for specified command‑line programs and reports each program’s installed version. It accepts a list of command names as arguments, prints a check‑mark with the version when found, and a cross when absent. The exit status equals the number of missing commands, allowing scripts to react to unavailable tools.

Typical usage is in shell scripts or CI pipelines where a project needs to verify that required binaries such as node, git, java, or custom tools are present before proceeding. A simple conditional can invoke the command and act on its success, and the same logic works when the script is fetched and executed directly from the Internet.

Installation consists of a single Bash script with no external dependencies beyond Bash itself. Users can place the script in their PATH, install via Homebrew, asdf, or other package managers, or download it with curl. A optional `.hasrc` file in the current directory can list default commands to check, and environment variable `HAS_ALLOW_UNSAFE` enables checking of non‑whitelisted names.