# webhook mit Homebrew, apk, apt, MacPorts, Nix, pacman, scoop installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für webhook in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:webhook ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install webhook ``` Evidenz: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install webhook ``` Evidenz: MacPorts ports tree: net/webhook/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - apk (92%): ```sh sudo apk add webhook ``` Evidenz: Alpine Linux edge package indexes: webhook from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz - Debian apt (92%): ```sh sudo apt install webhook ``` Evidenz: Debian stable package indexes: webhook from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz - Nix (92%): ```sh nix profile install nixpkgs#webhook ``` Evidenz: nixpkgs package indexes: pkgs/by-name/we/webhook/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S webhook ``` Evidenz: Arch Linux sync databases: webhook from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ### Windows - Scoop (92%): ```sh scoop install main/webhook ``` Evidenz: Scoop official bucket manifest trees: bucket/webhook.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Paketfakten - **Paketschlüssel:** brew:webhook - **Paketmanager:** Homebrew - **Version:** 2.8.3 - **Quellzusammenfassung:** Lightweight, configurable incoming webhook server - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-07-25T22:40:19+02:00 - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - webhook (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 2.8.3 ## Projektgeschichte und Nutzung webhook is a small Go service for turning incoming HTTP requests into guarded command execution on a server. Its niche is deliberately plain: define hooks in JSON or YAML, expose HTTP endpoints, validate request data with rules, and run configured scripts or commands when a matching event arrives. ### Projektgeschichte The public GitHub repository was created on January 12, 2015, and its first listed GitHub release, webhook 1.0.4, was published on March 13, 2015. The project has continued as an MIT-licensed command-line daemon under Adnan Hadziabdic's `adnanh/webhook` repository, with later 2.x releases still appearing as of 2026. The README describes the tool as a lightweight configurable incoming webhook server written in Go. That framing has remained stable across the project's life: it is not a full automation platform, but a minimal bridge between webhook providers and local server-side commands. ### Adoptionsgeschichte webhook's adoption has been strongest in self-hosted and operations workflows where users want a single-purpose listener instead of a larger CI/CD or eventing system. The upstream README points to guides for automatic deployments, JIRA integration, Ansible AWX job triggers, Salt-based static-site deployment, Plex-to-Telegram notifications, and other practical automation examples. By July 2026 the GitHub repository showed roughly twelve thousand stars and hundreds of forks via the public GitHub API, a sign that it became a recognizable Unix-style building block for small webhook automation jobs. ### Wie es verwendet wird A typical setup defines one or more hooks in `hooks.json` or `hooks.yaml`. Each hook names an id, a command to execute, optional working directory and argument mappings, and trigger rules that can inspect headers, payload fields, or query parameters before the command runs. Administrators commonly run webhook as a long-lived service behind a firewall, reverse proxy, or systemd unit, then wire providers such as GitHub, GitLab, monitoring systems, or chat tools to call the hook endpoint. Its package-nerd appeal is that the behavior is transparent: HTTP in, rule check, process execution out. ### Warum Paket-Nerds sich dafür interessieren webhook matters because it packages a common shell-ops pattern without demanding a workflow server. For people maintaining small servers, lab machines, media boxes, or personal deployment targets, it is the sort of boring CLI that replaces a pile of ad hoc CGI scripts while still feeling close to the shell. ### Zeitleiste - 2015-01-12: Public GitHub repository `adnanh/webhook` created. - 2015-03-13: First listed GitHub release, webhook 1.0.4, published. - 2020-05-12: webhook 2.7.0 released. - 2020-12-06: webhook 2.8.0 released. - 2026-02-12: webhook 2.8.3 released. ### Related projects - webhook sits near lightweight automation tools such as shell scripts, cron jobs, systemd units, and small CI deploy hooks. It overlaps with larger CI/CD systems only at the edge where an external HTTP event needs to trigger a local command. ### Quellen - - - - ## Sicherheitshinweise broad file, network, media, or database tool signal. - **Geiger-Risiko:** blue / mittel - broad file, network, media, or database tool signal ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: hooks.json, hooks.yaml ## Credential files - Unix: hooks.json, hooks.yaml ## Andere Paketmanager-Einträge - Debian apt - webhook - 2.8.0-4+b19: normalized package name match | Debian stable package indexes: webhook from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Small server for creating HTTP endpoints (hooks) | https://github.com/adnanh/webhook - Nix - webhook: normalized package name match | nixpkgs package indexes: pkgs/by-name/we/webhook/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Ubuntu apt - webhook - 2.8.0-4build1: normalized package name match | Ubuntu 24.04 LTS package indexes: webhook from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Small server for creating HTTP endpoints (hooks) | https://github.com/adnanh/webhook - apk - webhook - 2.8.3-r4: normalized package name match | Alpine Linux edge package indexes: webhook from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Lightweight configurable webhooks server | https://github.com/adnanh/webhook - pacman - webhook - 2.8.3-1: normalized package name match | Arch Linux sync databases: webhook from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A lightweight incoming webhook server to run shell commands | https://github.com/adnanh/webhook - MacPorts - webhook: normalized package name match | MacPorts ports tree: net/webhook/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 - Scoop - main/webhook: normalized package name match | Scoop official bucket manifest trees: bucket/webhook.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/webhook.yml](https://github.com/mxcl/pkgdb/blob/main/combined/webhook.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph