# Install opendoor with Homebrew

CLI for web reconnaissance, directory discovery, and exposure assessment. Version 5.18.0 via Homebrew; verified 2026-08-02.

## Install

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

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install opendoor
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:opendoor
- **Package manager:** Homebrew
- **Version:** 5.18.0
- **Source summary:** CLI for web reconnaissance, directory discovery, and exposure assessment
- **Homepage:** <https://github.com/stanislav-web/OpenDoor>
- **Last updated:** 2026-08-02T18:07:45Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- opendoor (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 5.18.0
## Project history and usage

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.

### Project history

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.

### Adoption history

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.

### How it is used

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.

### Why package nerds care

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


## Security Notes

No matching local secret-handling manifest was found for opendoor. Nucleus package metadata is still published here so future coverage has a stable package URL.



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