• Name: scopewatch
• Version: 0.1.0 (Git tag: v0.1.0)
• Homepage: https://github.com/zipperswag111/scopewatch
• Download: https://github.com/zipperswag111/scopewatch/archive/refs/tags/v0.1.0.tar.gz
• Author: scopewatch contributors
• Licence: MIT
• Description: scopewatch is an evidence-first external asset-drift auditor for explicitly authorized domains. It normalizes Certificate Transparency observations, optional account-backed SecurityTrails and WhoisXML data, user-supplied historic Rapid7 Sonar FDNS baselines, and optional wordlist candidates. Each result is labelled observed, historic, candidate, verified, or source-error with provenance. Candidate labels are never represented as discovered assets. Optional verification is DNS resolution only.
• Dependencies: Python 3.10+; no third-party runtime Python dependencies. Optional inputs: SecLists/other local wordlists, user API keys for SecurityTrails and WhoisXML, and a user-downloaded Rapid7 FDNS file.
• Similar tools: Amass and subfinder provide broad enumeration; httpx and naabu provide later probing. scopewatch focuses narrowly on evidence status, provenance, historic drift, and an explicit authorization workflow.
• Activity: Initial public release on November 4, 2026. Development and releases are tracked in the public GitHub repository.
• How to install: python3 -m pip install . && scopewatch --version. For Debian packaging: dpkg-buildpackage -us -uc -b, then install the generated .deb package.
• Debian packaging: Included in the source release under debian/. The package is architecture-independent and installs the scopewatch command.

Data policy: scopewatch does not bundle, mirror, or redistribute commercial/passive datasets or API keys. Provider integrations require the operator's own account and compliance with provider terms. The tool is not a mass scanner, exploit tool, login tester, credential tool, or brute-force engine.