# jeffbski/wait-on

wait-on is a cross-platform command line utility and Node.js API which will wait for files, ports, sockets, and http(s) resources to become available

Repository: https://github.com/jeffbski/wait-on
Canonical: https://ross.abutalabs.com/products/wait-on
Language: JavaScript
License: MIT
License Family: permissive
Last push: 2026-07-21T20:56:18+00:00

## Health v2 (maintenance only)
Score: 91/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 93, release rhythm 82, longevity 100
- inputs: {"age_days": 4059, "days_push": 43, "days_rel": 43, "gap_med": 50.0, "n_releases_24m": 13}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1981, forks 86 (observed 2026-08-28T04:06:01.770678+00:00)

## What it is
wait-on is a cross-platform CLI utility and Node.js API that waits for files, TCP ports, Unix sockets, and HTTP(S) resources to become available (or unavailable in reverse mode) before proceeding. It is commonly used to sequence commands in scripts and CI pipelines, such as waiting for a server to start before running tests.

## Use cases
- wait for a dev server to start before running tests
- block a script until a file stops growing
- wait for a TCP port to be listening
- wait for an HTTP endpoint to return 2XX
- wait for a service to shut down before continuing
- sequence docker compose startup dependencies
- poll a health check endpoint in CI

## When to choose
- you need to gate a command on files, ports, sockets, or HTTP endpoints becoming ready
- you want a simple cross-platform (Linux/macOS/Windows) wait utility with zero config
- you need both a CLI and a programmatic Node.js API
- you want reverse mode to wait for resources to disappear

## When to avoid
- you need complex orchestration beyond simple resource readiness checks
- you want health checks with custom logic beyond HTTP 2XX status
- you are not in a Node.js-available environment
- you need service discovery or distributed coordination rather than local readiness polling

## Facets
- artifact type: cli-tool
- maturity: stable
- function: cli, developer-tools, workflow-automation, http-client
- domain: developer-tools
- platform: cli, cross-platform, windows
- tags: wait-for-resources, port-waiting, file-waiting, tcp-sockets, http-health-check, npm-package, reverse-mode, service-readiness, command-line, devops, automation, nodejs, linux, macos

## Member repositories
- jeffbski/wait-on (main) score 91

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:01.770678+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:03:58.294306+00:00, confidence not recorded.
  - readme: https://github.com/jeffbski/wait-on (fetched 2026-08-28T04:06:01.770678+00:00, sha 47ca4e3cfd17)
  - registry_npm: https://registry.npmjs.org/wait-on (fetched 2026-08-29T10:43:43.988197+00:00, sha 45061720ef81)
- Data as of 2026-08-30T08:39:29.467469+00:00.