# fsw mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für fsw in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:fsw
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install fsw
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:fsw
- **Paketmanager:** Homebrew
- **Version:** 1.3.9
- **Quellzusammenfassung:** File change monitor with multiple backends
- **Homepage:** <https://emcrisostomo.github.io/fsw/>
- **Repository:** <https://github.com/emcrisostomo/fsw>
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- fsw (Alias)
- fswatch-run (Alias)
- fswatch-run-bash (Alias)
- fswatch-run-zsh (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 1.3.9
## Projektgeschichte und Nutzung

fsw was Enrico M. Crisostomo's 2013-2014 cross-platform file-change monitor, later merged into fswatch.

### Projektgeschichte

The fsw README says it was written at the end of 2013 to provide both a drop-in replacement for Alan Dipert's original fswatch and a common front end for OS X FSEvents, BSD kqueue, and Linux inotify.

In April 2014, the fsw and fswatch authors agreed to merge the two programs, with Enrico Crisostomo taking over fswatch maintenance. The fsw README states that development would continue in the main fswatch repository and that fsw would likely be frozen.

### Adoptionsgeschichte

fsw's adoption history is mostly transitional. The supplied package data shows a Homebrew package, but the official README redirected long-term users toward fswatch after the merger.

### Wie es verwendet wird

fsw accepts a list of paths and emits change events when those files or directories are modified. Its project page documents four monitors: OS X FSEvents, BSD kqueue, Linux inotify, and a portable stat-based polling monitor.

The project page recommends release tarballs for normal users and reserves repository checkouts for developers with the GNU Build System.

### Warum Paket-Nerds sich dafür interessieren

fsw is historically interesting because it explains how the modern fswatch package absorbed a parallel cross-platform watcher effort. For package maintainers, it is mainly a predecessor and compatibility waypoint rather than the active upstream.

### Zeitleiste

- 2009: Alan Dipert wrote the first fswatch implementation for OS X FSEvents.
- 2013: Enrico M. Crisostomo wrote fsw as a broader cross-platform front end.
- 2014: fsw public repository created.
- 2014: fsw and fswatch merged, with future development continuing in fswatch.

### Related projects

- fswatch is the direct successor project and long-term upstream.
- fsw relates to the operating-system event APIs it wrapped: FSEvents, kqueue, inotify, and stat-based polling.

### Quellen

- <https://api.github.com/repos/emcrisostomo/fsw>
- <https://emcrisostomo.github.io/fsw>
- <https://github.com/emcrisostomo/fsw>
- <https://raw.githubusercontent.com/emcrisostomo/fsw/master/README.md>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Combined YAML source

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


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph