# opendoor mit Homebrew installieren

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

## Installation

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

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install opendoor
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:opendoor
- **Paketmanager:** Homebrew
- **Version:** 5.18.0
- **Quellzusammenfassung:** CLI for web reconnaissance, directory discovery, and exposure assessment
- **Homepage:** <https://github.com/stanislav-web/OpenDoor>
- **Zuletzt aktualisiert:** 2026-08-02T18:07:45Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- opendoor (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

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.

### Projektgeschichte

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.

### Adoptionsgeschichte

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.

### Wie es verwendet wird

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.

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

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.

### Quellen

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


## Sicherheitshinweise

Für opendoor wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.



## Combined YAML source

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


## Quellen

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