# Installer notify avec Homebrew, Nix

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de notify pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:notify
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install notify
```

  Preuve: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#notify
```

  Preuve: nixpkgs package indexes: pkgs/by-name/no/notify/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Faits du paquet

- **Clé du paquet:** brew:notify
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.0.7
- **Résumé source:** Stream the output of any CLI and publish it to a variety of supported platforms
- **Page d'accueil:** <https://docs.projectdiscovery.io/tools/notify/overview>
- **Dépôt:** <https://github.com/projectdiscovery/notify>
- **Dernière mise à jour:** 2026-07-26T19:43:16+02:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- notify (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 1.0.7
## Historique du projet et usages

ProjectDiscovery notify is a Go CLI for streaming command output or file contents to notification providers such as Slack, Discord, Telegram, Pushover, email, Microsoft Teams, Google Chat, Gotify, and custom webhooks.

### Historique du projet

The tag history begins with v0.0.1 on 2020-11-04 and reaches v1.0.0 on 2021-08-22. The release line continued through v1.0.7 on 2024-10-31, which matches the stable version in the Homebrew formula metadata checked for this batch.

notify belongs to the ProjectDiscovery ecosystem, so its history is tied to security and recon workflows rather than generic desktop notifications. The README's examples show subfinder output piped into notify, making it part of the common ProjectDiscovery pattern of chaining small CLI tools.

### Historique d'adoption

Adoption is strongest among security automation users who already run ProjectDiscovery tools. Homebrew formula analytics reported 217 installs over the 365-day window, which likely understates overall use because the README emphasizes go install and ProjectDiscovery also publishes Docker images.

### Modes d'utilisation

Typical usage is to configure provider credentials in ~/.config/notify/provider-config.yaml, then pipe another command's output into notify or send an output file with -data. Flags cover bulk mode, per-message character limits, provider selection, provider IDs, rate limiting, proxying, custom formatting, and custom webhooks.

The practical package-nerd distinction from noti is that notify is pipeline-oriented: it forwards output from tools, scans, or files to shared channels. It is less about telling one local user that a command finished and more about routing results to team notification systems.

### Pourquoi les passionnés de paquets s'y intéressent

notify is a small but important piece of security-tool plumbing. It packages notification fanout as a composable Unix filter, which keeps recon and monitoring scripts from embedding Slack/Discord/Telegram webhook logic everywhere.

### Chronologie

- 2020-11-04: v0.0.1 tag.
- 2021-08-22: v1.0.0 tag.
- 2024-10-31: v1.0.7 tag, matching the Homebrew stable formula version checked here.

### Related projects

- ProjectDiscovery subfinder, httpx, nuclei, Slack, Discord, Telegram, Pushover, Microsoft Teams, Google Chat, Gotify.

### Sources

- <https://docs.projectdiscovery.io/tools/notify/overview>
- <https://formulae.brew.sh/api/formula/notify.json>
- <https://github.com/projectdiscovery/notify>
- <https://github.com/projectdiscovery/notify/releases>


## Notes de sécurité

broad file, network, media, or database tool signal.

- **Risque Geiger:** blue / moyen
- 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: ~/.config/notify/config.yaml, ~/.config/notify/provider-config.yaml

## Credential files

- Unix: ~/.config/notify/provider-config.yaml
## Autres enregistrements de gestionnaires de paquets

- Nix - notify: normalized package name match | nixpkgs package indexes: pkgs/by-name/no/notify/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/notify.yml](https://github.com/mxcl/pkgdb/blob/main/combined/notify.yml)


## Sources

- 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