macOS
Homebrewverifiziert · 100%
brew install wait4xlocal Homebrew formula metadata
brew / Rang 9181
wait4x mit Homebrew, apk, Nix, zypper, scoop installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für wait4x in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Linux
Alpine Linux apkverifiziert · 92%
sudo apk add wait4xAlpine Linux edge package indexes · wait4x · Quelle: dl-cdn.alpinelinux.org
Nixverifiziert · 92%
nix profile install nixpkgs#wait4xnixpkgs package indexes · pkgs/by-name/wa/wait4x/package.nix · Quelle: api.github.com
openSUSE zypperverifiziert · 92%
sudo zypper install wait4xopenSUSE Tumbleweed package metadata · wait4x · Quelle: download.opensuse.org
Windows
Scoopverifiziert · 92%
scoop install extras/wait4xScoop official bucket manifest trees · bucket/wait4x.json · Quelle: api.github.com
Überblick
Paketzusammenfassung
Wait for a port or a service to enter the requested state
Projektlinks
Befehle und Aliase
- wait4x
Verlauf
Projektgeschichte und Nutzung
Wait4X is a Go-based readiness-waiting tool for scripts, CI jobs, containers, and local development. Its job is deliberately narrow: block until a port, protocol endpoint, database, message broker, or other service reaches the expected state, then optionally run a command.
Projektgeschichte
The GitHub repository was created on November 1, 2019, and GitHub release metadata shows v0.1.0 published on February 8, 2020. The project later adopted the `wait4x.dev/v3` module path and documents itself as a lightweight, zero-dependency tool for modern infrastructure readiness checks.
By 2025 the release series had reached v3.6.0, and the README described a broader surface than simple TCP waiting: TCP, HTTP, DNS, Redis, MySQL, PostgreSQL, MongoDB, Kafka, RabbitMQ, InfluxDB, Temporal, reverse checks, parallel checks, exponential backoff, and command execution after checks.
Adoptionsgeschichte
Wait4X lives in the same operational niche as `wait-for-it`, `dockerize`, Kubernetes readiness checks, and ad hoc shell loops, but its pitch is one static cross-platform binary with service-aware checks. As of July 2, 2026, GitHub API metadata showed about 1,339 stars and 54 forks, which is meaningful adoption for a focused infrastructure CLI.
Wie es verwendet wird
Typical usage is inline in automation: `wait4x tcp localhost:5432`, `wait4x http https://example.com/health --expect-status-code 200`, or `wait4x postgresql postgres://...` before a test suite or startup script continues. The README also shows multiple targets checked in parallel and an `--invert-check` mode for waiting until a service becomes unavailable.
Because it can run a command after readiness succeeds, Wait4X often replaces a shell loop in Docker entrypoints, CI workflow steps, and local scripts where a database, cache, broker, or API needs to be up before the next process starts.
Warum Paket-Nerds sich dafür interessieren
Its package-nerd significance is the consolidation of many tiny readiness patterns into one binary. It does not define a protocol or framework, but it is useful glue in the places where package managers, containers, and CI systems expose race conditions between service startup and test execution.
Zeitleiste
- November 1, 2019: the wait4x/wait4x repository was created on GitHub.
- February 8, 2020: v0.1.0 was published as an early GitHub release.
- October 20, 2025: v3.6.0 was published, showing the project had continued into a v3 line with a wider readiness-check surface.
- July 2, 2026: GitHub API metadata showed the project still present as a moderate-sized infrastructure CLI repository.
Related projects
- Related tools include `wait-for-it`, `dockerize`, and health-check mechanisms in Docker Compose and Kubernetes. Wait4X differs by shipping a single CLI with multiple protocol and service-specific checks rather than relying only on raw TCP ports or shell scripting.
Quellen
Sicherheitslage
Noch keine Protected-Tool-Abdeckung gefunden
Für wait4x wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.
Installationsverhalten
- Es wurden keine Homebrew-Bottle-Metadaten erfasst.
Empfohlene Prüfung
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
wait4x | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
Aktualität
Version und Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Seite generiert2026-08-03
Manager-Version3.6.0
Manager aktualisiert2026-05-09
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
- OKEs wurden keine Aktualitätswarnungen generiert.
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:wait4x |
|---|---|
| Version | 3.6.0 |
| Paketmanager | Homebrew |
| Homepage | https://wait4x.dev |
| Repository | https://github.com/wait4x/wait4x |
| Zuletzt aktualisiert | 2026-05-09T15:13:04Z |
| Pulse | updated |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Source-Datenbank-Treffer
Andere Paketmanager-Einträge
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
Nix95%
wait4x
nix profile install nixpkgs#wait4x- normalized package name match
- Abgeglichen nach: Wait4x
apk95%
wait4x 3.6.0-r3
Wait4X allows you to wait for a port or a service to enter the requested state
sudo apk add wait4x- License: Apache-2.0
- Architecture: x86_64
- Source Package: wait4x
- 1 Abhängigkeiten
- 1 stellt bereit
- normalized package name match
- Abgeglichen nach: Wait4x
apk95%
wait4x-bash-completion 3.6.0-r3
Bash completions for wait4x
sudo apk add wait4x-bash-completion- License: Apache-2.0
- Architecture: x86_64
- Source Package: wait4x
- normalized package name match
- Abgeglichen nach: Wait4x
apk95%
wait4x-doc 3.6.0-r3
Wait4X allows you to wait for a port or a service to enter the requested state (documentation)
sudo apk add wait4x-doc- License: Apache-2.0
- Architecture: x86_64
- Source Package: wait4x
- normalized package name match
- Abgeglichen nach: Wait4x
apk95%
wait4x-fish-completion 3.6.0-r3
Fish completions for wait4x
sudo apk add wait4x-fish-completion- License: Apache-2.0
- Architecture: x86_64
- Source Package: wait4x
- normalized package name match
- Abgeglichen nach: Wait4x
apk95%
wait4x-zsh-completion 3.6.0-r3
Zsh completions for wait4x
sudo apk add wait4x-zsh-completion- License: Apache-2.0
- Architecture: x86_64
- Source Package: wait4x
- normalized package name match
- Abgeglichen nach: Wait4x
zypper95%
wait4x 3.6.0-1.6
Wait for a port or a service to enter the requested state
https://github.com/wait4x/wait4x
sudo zypper install wait4x- License: Apache-2.0
- Category: Unspecified
- Architecture: x86_64
- Source Package: wait4x
- 1 Abhängigkeiten
- 1 stellt bereit
- normalized package name match
- Abgeglichen nach: Wait4x
Scoop95%
extras/wait4x
scoop install extras/wait4x- normalized package name match
- Abgeglichen nach: Wait4x
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- Geiger risk classifier
- cross-ecosystem install command graph
- curated package history
- external package-manager database matches
- pkg.so package database
- pkgdb category and tag curation