Breachwatch

pip install cognis-breachwatch
breachwatch scan .            # → prioritized findings in seconds

🔎 Example output

Real, reproducible output from the tool — runs offline:

$ breachwatch-emit --version
breachwatch 0.1.0

$ breachwatch-emit --help
usage: breachwatch [-h] [--version] {triage} ...

Personal breach aggregator: HIBP + DeHashed + stealer-log triage.

positional arguments:
  {triage}
    triage    Aggregate + risk-score breach exposures from local sources.

options:
  -h, --help  show this help message and exit
  --version   show program's version number and exit

Blocks above are real breachwatch output — reproduce them from a clone.

Sample result format (illustrative values — run on your own data for real findings):

{
"findings": [
    {
        "id": "1234567890",
        "title": "Potential Breach: Unauthorised Access",
        "description": "An unauthorised user accessed a sensitive database.",
        "created_by": "John Doe",
        "created_at": "2023-02-15T14:30:00Z"
    }
]
}

Usage — step by step

breachwatch is a personal breach aggregator that triages and risk-scores exposures from local sources (HIBP / DeHashed / stealer logs).

1. Install:

   pip install -e .
   

2. Triage from a JSON config describing identities + sources:

   breachwatch triage config.json
   

3. Filter by severity and read JSON output:

   breachwatch triage config.json --min-severity medium --format json
   

4. Use the exit code — --fail-on returns exit code 2 when any exposure meets/exceeds the given severity:

   breachwatch triage config.json --fail-on high
   

5. Automate in cron/CI:

   breachwatch triage config.json --format json --fail-on high > exposures.json
   

Contents

• Why breachwatch? · Features · Quick start · Example · Architecture · AI stack · How it compares · Integrations · Install anywhere · Related · Contributing

Why breachwatch?

Personal breach aggregator — HIBP + DeHashed + stealer-log triage — without standing up heavyweight infrastructure.

breachwatch is single-purpose, scriptable, and self-hostable: point it at a target, get prioritized results in the format your workflow already speaks (table · JSON · SARIF), gate CI on it, and let agents drive it over MCP.

Features

• ✅ Redact
• ✅ Severity For
• ✅ Parse Hibp
• ✅ Parse Dehashed
• ✅ Parse Stealer Log
• ✅ Triage
• ✅ Load Sources
• ✅ Runs on Linux/macOS/Windows · Docker · devcontainer
• ✅ Ports in Python, JavaScript, Go, and Rust (ports/)

Quick start

pip install cognis-breachwatch
breachwatch --version
breachwatch scan .                       # scan current project
breachwatch scan . --format json         # machine-readable
breachwatch scan . --fail-on high        # CI gate (non-zero exit)

Example

$ breachwatch scan .
  [HIGH    ] BRE-001  example finding             (./src/app.py)
  [MEDIUM  ] BRE-002  another signal              (./config.yaml)

  2 findings · risk score 5 · 38ms

Architecture

flowchart LR
  IN[input] --> P[breachwatch<br/>analyze + score]
  P --> OUT[report]

Use it from any AI stack

breachwatch is interoperable with every popular way of using AI:

• MCP server — breachwatch mcp (Claude Desktop, Cursor, Cognis.Studio, uncensored-fleet)
• OpenAI-compatible / JSON — pipe breachwatch scan . --format json into any agent or LLM
• LangChain · CrewAI · AutoGen · LlamaIndex — wrap the CLI/JSON as a tool in one line
• CI / scripts — exit codes + SARIF for non-AI pipelines

How it compares

	Cognis breachwatch	typical tools
Self-hostable, no account	✅	varies
Single command, zero config	✅	⚠️
JSON + SARIF for CI	✅	varies
MCP-native (AI agents)	✅	❌
Polyglot ports (JS/Go/Rust)	✅	❌
Open license	✅ COCL	varies

Integrations

Pipes into your stack: SARIF for code-scanning, JSON for anything, an MCP server (breachwatch mcp) for AI agents, and a webhook forwarder for SIEM/Slack/Jira. See docs/INTEGRATIONS.md.

Install — every way, every platform

pip install "git+https://github.com/cognis-digital/breachwatch.git"    # pip (works today)
pipx install "git+https://github.com/cognis-digital/breachwatch.git"   # isolated CLI
uv tool install "git+https://github.com/cognis-digital/breachwatch.git" # uv
pip install cognis-breachwatch                                          # PyPI (when published)
docker run --rm ghcr.io/cognis-digital/breachwatch:latest --help        # Docker
brew install cognis-digital/tap/breachwatch                             # Homebrew tap
curl -fsSL https://raw.githubusercontent.com/cognis-digital/breachwatch/main/install.sh | sh

Linux	macOS	Windows	Docker	Cloud
scripts/setup-linux.sh	scripts/setup-macos.sh	scripts/setup-windows.ps1	docker run ghcr.io/cognis-digital/breachwatch	DEPLOY.md (AWS/Azure/GCP/k8s)

Related Cognis tools

• recall — Privacy-first local RAG over personal data — encrypted, audit-logged
• optout — Automated data-broker opt-out engine — top 50 brokers, CCPA/GDPR letters
• vaultmap — Personal asset & account inventory — estate-planning-grade encrypted
• piicomb — Local PII discovery in your own files — SSN/CC/passport/DL/email/phone/DOB
• trackblock — Family phone stalkerware audit — MVT-class iOS/Android forensics
• privacyshell — Hardened browser profile generator — Firefox / LibreWolf / Brave

Explore the suite → 🗂️ all 170+ tools · ⭐ awesome-cognis · 🔗 cognis-sources · 🤖 uncensored-fleet · 🧠 engram

Contributing

PRs, new rules, and demo scenarios are welcome under the collaboration-pull model — see CONTRIBUTING.md and SECURITY.md.

⭐ If breachwatch saved you time, star it — it genuinely helps others find it.

Interoperability

{} composes with the 300+ tool Cognis suite — JSON in/out and a shared OpenAI-compatible /v1 backbone. See INTEROP.md for the suite map, composition patterns, and reference stacks.

License

Source-available under the Cognis Open Collaboration License (COCL) v1.0 — free for personal, internal-evaluation, research, and educational use; commercial / production use requires a license ([email protected]). See LICENSE.

---