# Installer feroxbuster avec Homebrew, Nix, zypper, scoop, winget

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

## installation

```sh
sudo av install brew:feroxbuster
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install feroxbuster
```

  Preuve: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#feroxbuster
```

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

- zypper (92%):

```sh
sudo zypper install feroxbuster
```

  Preuve: openSUSE Tumbleweed package metadata: feroxbuster from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

### Windows

- Scoop (92%):

```sh
scoop install main/feroxbuster
```

  Preuve: Scoop official bucket manifest trees: bucket/feroxbuster.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

- winget (92%):

```sh
winget install --id epi052.feroxbuster -e
```

  Preuve: Windows Package Manager source index: epi052.feroxbuster from https://cdn.winget.microsoft.com/cache/source.msix

## Faits du paquet

- **Clé du paquet:** brew:feroxbuster
- **Gestionnaire de paquets:** Homebrew
- **Version:** 2.13.1
- **Résumé source:** Fast, simple, recursive content discovery tool written in Rust
- **Page d'accueil:** <https://epi052.github.io/feroxbuster>
- **Dépôt:** <https://github.com/epi052/feroxbuster>
- **Dernière mise à jour:** 2026-06-22T14:03:19-07:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- feroxbuster (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

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

feroxbuster is a Rust command-line tool for recursive web content discovery. Its README frames it as a forced-browsing tool: it combines brute force with wordlists to find unlinked resources, directories, files, and other predictable locations in web applications.

### Historique du projet

The public GitHub repository was created in August 2020, and crates.io records the first `feroxbuster` crate release in October 2020. The project reached 1.0.0 within days of the initial crate publication and continued through a long 2.x line with regular releases.

The project documentation later moved from a very large README to a GitHub Pages documentation site, while the README retained quick-start installation and usage examples. The project also added an updater in the 2.x era and documents official distribution channels to avoid domain impersonation.

### Historique d'adoption

feroxbuster's adoption path follows the Rust security-tool pattern: GitHub releases and crates.io for early users, then OS package managers and security distributions for everyday use. The README documents Kali, Homebrew, winget, Chocolatey, install scripts, and project docs for other platforms; the input package metadata also records Nix, Scoop, winget, and zypper packaging.

Crates.io metadata records more than 130,000 downloads and the repository README displays badges for GitHub and crates.io downloads. Those numbers support a real package-manager footprint for a specialized security CLI.

### Modes d'utilisation

Typical use passes a target URL, wordlist-derived extensions, filters for status codes or response sizes, recursion controls, headers, query parameters, proxy settings, and output options. The README examples show piping targets through standard input, proxying through Burp or SOCKS, passing authorization headers, and sending JSON or form bodies.

In practice feroxbuster is used during web application testing to enumerate hidden or unlinked resources. Package users care about fast installation, shell completions, a default config path on security distributions, and reproducible CLI behavior across Linux, macOS, and Windows.

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

feroxbuster is significant because it became one of the recognizable Rust replacements in the directory-enumeration and content-discovery space. It packages as a single CLI but has enough operational surface to matter: config files, completions, man pages, update behavior, and multiple binary distribution paths.

For maintainers, it is also a good example of security-tool packaging where provenance matters. The README explicitly warns about an unrelated impersonating domain and lists official download channels, which is unusually relevant package metadata for a pentesting tool.

### Chronologie

- 2020: Public GitHub repository created.
- 2020: First crates.io release and 1.0.0 release published.
- 2023: 2.10.x release line appears on crates.io.
- 2025: crates.io records the 2.13.1 release.

### Related projects

- feroxbuster is related to forced-browsing and directory-enumeration tools used in web security testing, and it is commonly paired with wordlists, proxies such as Burp Suite, and shell pipelines for target and result processing.

### Sources

- <https://github.com/epi052/feroxbuster>
- <https://github.com/epi052/feroxbuster/blob/main/README.md>
- <https://api.github.com/repos/epi052/feroxbuster>
- <https://crates.io/crates/feroxbuster>
- <https://formulae.brew.sh/formula/feroxbuster>


## Notes de sécurité

narrow executable package without higher-risk signals.

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


## 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

- Linux: /etc/feroxbuster/ferox-config.toml
## Autres enregistrements de gestionnaires de paquets

- Nix - feroxbuster: normalized package name match | nixpkgs package indexes: pkgs/by-name/fe/feroxbuster/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- zypper - feroxbuster - 2.13.1-1.6: normalized package name match | openSUSE Tumbleweed package metadata: feroxbuster from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | A recursive content discovery tool | https://epi052.github.io/feroxbuster-docs/
- zypper - feroxbuster-bash-completion - 2.13.1-1.6: normalized package name match | openSUSE Tumbleweed package metadata: feroxbuster-bash-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Bash Completion for feroxbuster | https://epi052.github.io/feroxbuster-docs/
- Scoop - main/feroxbuster: normalized package name match | Scoop official bucket manifest trees: bucket/feroxbuster.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- winget - epi052.feroxbuster: normalized package name match | Windows Package Manager source index: epi052.feroxbuster from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

View the package source record on GitHub. [combined/feroxbuster.yml](https://github.com/mxcl/pkgdb/blob/main/combined/feroxbuster.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
