# Installer deadfinder avec Homebrew

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

## installation

```sh
sudo av install brew:deadfinder
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install deadfinder
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:deadfinder
- **Gestionnaire de paquets:** Homebrew
- **Version:** 2.0.2
- **Résumé source:** Finds broken links
- **Page d'accueil:** <https://deadfinder.hahwul.com>
- **Dépôt:** <https://github.com/hahwul/deadfinder>
- **Dernière mise à jour:** 2026-06-15T10:20:14-04:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- deadfinder (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

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

DeadFinder is a command-line broken-link scanner for web pages, URL lists, and sitemaps. Its package-manager appeal is straightforward: it is a single-purpose audit tool that can run locally, in Docker, or inside CI.

### Historique du projet

The project began as a Ruby-gem lineage and later moved active development to a Crystal implementation for version 2.0.0 and later. The official changelog describes the Crystal rewrite, root-level Crystal project layout, compatibility harness against v1 Ruby output, and migration of the GitHub Action away from a Docker entrypoint toward a composite action that downloads release binaries.

### Historique d'adoption

The project documents Homebrew, Docker, prebuilt release binaries, Nix, source builds, distro release artifacts, AUR, and Snap as installation routes. It also ships an official GitHub Action interface, which made it natural for package users to wire dead-link checks into documentation and website workflows.

### Modes d'utilisation

Common CLI use is organized around subcommands for scanning a single URL, a sitemap, a file, or piped standard input. Output can be written as structured formats including JSON, YAML, TOML, CSV, and SARIF, with options for concurrency, timeouts, filtering, custom headers, proxy use, coverage reporting, and visualization.

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

DeadFinder sits in the practical overlap between web maintenance, SEO hygiene, security review, and CI automation. For package nerds, the v1-to-v2 runtime change is also a tidy example of a tool keeping its command-line contract while swapping implementation language and release packaging model.

### Chronologie

- 2025: 1.10.0 release continued the Ruby-gem lineage while noting active development had moved to the Crystal rewrite.
- 2026: 2.0.0 made the Crystal implementation the supported runtime and moved Ruby gem publishing to the legacy branch.
- 2026: 2.0.2 fixed composite GitHub Action release-asset handling.

### Related projects

- Related link-checking and site-quality tools include generic HTTP link checkers, sitemap crawlers, and CI documentation validators; DeadFinder distinguishes itself with a small native CLI plus an official GitHub Action path.

### Sources

- <https://deadfinder.hahwul.com>
- <https://deadfinder.hahwul.com/docs/getting-started/installation/>
- <https://github.com/hahwul/deadfinder/blob/main/CHANGELOG.md>
- <https://github.com/hahwul/deadfinder/releases>


## Notes de sécurité

narrow executable package without higher-risk signals.

- **Risque Geiger:** vert / faible
- narrow executable package without higher-risk signals


## Combined YAML source

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


## Sources

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