# terminal-notifier mit Homebrew, MacPorts, Nix installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für terminal-notifier in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:terminal-notifier ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install terminal-notifier ``` Evidenz: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install terminal-notifier ``` Evidenz: MacPorts ports tree: aqua/terminal-notifier/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - Nix (92%): ```sh nix profile install nixpkgs#terminal-notifier ``` Evidenz: nixpkgs package indexes: pkgs/by-name/te/terminal-notifier/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Paketfakten - **Paketschlüssel:** brew:terminal-notifier - **Paketmanager:** Homebrew - **Version:** 2.0.0 - **Quellzusammenfassung:** Send macOS User Notifications from the command-line - **Homepage:** - **Repository:** - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - terminal-notifier (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 2.0.0 ## Projektgeschichte und Nutzung terminal-notifier is a macOS command-line bridge to User Notifications. It became a common small utility for shell scripts, build systems, Ruby projects, and package-manager users that wanted Notification Center messages without writing a Cocoa application. ### Projektgeschichte The GitHub repository was created in July 2012, the year Apple introduced Notification Center on OS X Mountain Lion. The README explains the central packaging compromise: the tool was historically distributed as an application bundle because NSUserNotification did not work from a plain Foundation command-line tool. The project grew around scriptable notification primitives: message text, title and subtitle, sounds, grouping and removal, opening URLs, activating apps, and setting sender or icon behavior. The README also documents a Ruby wrapper and a RubyGems installation path, which helped the tool circulate in Ruby-oriented automation as well as ordinary shell use. A notable maintenance chapter came in 2016 and 2017, when features from alerter were merged into terminal-notifier 1.7 and then removed again for 2.0.0. The README and 2.0.0 release notes frame the split as a decision to keep terminal-notifier and alerter as smaller specialized tools, with terminal-notifier dropping sticky notifications and action buttons. ### Adoptionsgeschichte terminal-notifier's README has long documented Homebrew installation alongside prebuilt releases and RubyGems. The input package facts also list Homebrew, MacPorts, and Nix, showing that it crossed from a GitHub utility into several package-manager ecosystems. The release history shows sustained maintenance through macOS platform changes: 1.5.0 in 2013 added piped message data, sender spoofing, sound support, and URL escaping; 1.6.x handled OS X 10.10 compatibility; 1.8.0 briefly changed distribution to a standard command-line app before 2.0.0 returned to the bundle model. ### Wie es verwendet wird Typical usage is to emit a desktop notification at the end of a long-running shell command, CI step, backup job, synchronization task, or local development workflow. The README examples show piped message data, custom icons, opening a URL when clicked, and activating a macOS app. The `-group` option is especially package-nerd friendly: scripts can replace or remove prior notifications under a stable group ID instead of spamming the notification center. The `-list` output is tab-separated, making it parseable from shell scripts. ### Warum Paket-Nerds sich dafür interessieren terminal-notifier matters in the Homebrew-era macOS CLI niche because it gave Unix-style scripts access to a native macOS UI affordance. It is the kind of package users install once and then wire into makefiles, deploy scripts, long compiles, package builds, and dotfile workflows. Its maintenance history also reflects a recurring packaging tension on macOS: command-line users want a simple executable, but Apple's notification APIs and App Store rules pushed the project toward an app-bundle distribution with caveats. ### Zeitleiste - 2012: GitHub repository created on July 15. - 2013: Release 1.5.0 added piped input, sender, sound, URL handling, and help support. - 2014: Release 1.6.1 added OS X 10.10 compatibility. - 2016: Release 1.7.0 merged alerter features such as reply and actions. - 2017: Release 1.8.0 made terminal-notifier a standard command-line app and deprecated OS X 10.8 and 10.9. - 2017: Release 2.0.0 removed alerter features and returned to a smaller focused tool. ### Related projects - alerter is the closest sibling project, split out for sticky notifications and action buttons. terminal-notifier also overlaps with scripting wrappers and package-manager recipes that expose macOS Notification Center from shell and Ruby workflows. ### Quellen - GitHub README: https://github.com/julienXX/terminal-notifier#readme - GitHub releases: https://github.com/julienXX/terminal-notifier/releases - GitHub repository metadata: https://api.github.com/repos/julienXX/terminal-notifier - Input source_facts.package-manager ## Sicherheitshinweise narrow executable package without higher-risk signals. - **Geiger-Risiko:** grün / niedrig - narrow executable package without higher-risk signals ## Andere Paketmanager-Einträge - Nix - terminal-notifier: normalized package name match | nixpkgs package indexes: pkgs/by-name/te/terminal-notifier/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - MacPorts - terminal-notifier: normalized package name match | MacPorts ports tree: aqua/terminal-notifier/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/terminal-notifier.yml](https://github.com/mxcl/pkgdb/blob/main/combined/terminal-notifier.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph