# Installer opendoor avec Homebrew

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

## installation

```sh
sudo av install brew:opendoor
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install opendoor
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:opendoor
- **Gestionnaire de paquets:** Homebrew
- **Version:** 5.18.0
- **Résumé source:** CLI for web reconnaissance, directory discovery, and exposure assessment
- **Page d'accueil:** <https://github.com/stanislav-web/OpenDoor>
- **Dernière mise à jour:** 2026-08-02T18:07:45Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- opendoor (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

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

OpenDoor is a Python command-line scanner for authorized web reconnaissance, directory discovery, and exposure assessment. It belongs to the family of directory-enumeration and web recon tools used before or alongside deeper vulnerability testing.

### Historique du projet

The Stanislav WEB repository presents OpenDoor as an OWASP-oriented web recon and directory discovery platform. Its documentation emphasizes practical scanner workflows such as path discovery, subdomain enumeration, fingerprint-first scanning, WAF detection, response filtering, resumable sessions, proxy/VPN transport workflows, and HTML reporting.

### Historique d'adoption

Evidence for broad historical adoption is thin, but the repository and Homebrew formula show enough packaging interest to treat it as more than a one-off script. Its package-manager footprint is narrow compared with older security tools, with Homebrew carrying the formula in this input set.

### Modes d'utilisation

Security researchers, penetration testers, bug bounty hunters, DevSecOps engineers, and developers use OpenDoor to identify exposed paths, login panels, directory listings, restricted resources, backup files, web shells, and related web assets during authorized assessments.

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

OpenDoor is package-nerd relevant because it turns a security workflow that is often a loose script plus wordlists into a named CLI package. Its packaging value is mainly reproducibility: a pinned scanner version, declared Python dependencies, and a consistent executable for local labs or CI exposure checks.

### Sources

- <https://formulae.brew.sh/formula/opendoor>
- <https://github.com/stanislav-web/OpenDoor>
- <https://github.com/stanislav-web/OpenDoor/wiki>
- <https://opendoor.readthedocs.io/>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour opendoor. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.



## Combined YAML source

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


## Sources

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