repowiserepowise

interplains / zero-breach-toolkit Architecture and code health

Free, open-source check for traces of mercenary spyware (Pegasus, Predator, Graphite, Candiru and more) on computers, Android phones and iPhone backups. Double-click apps for Windows, Mac and Linux, in 27 languages.

★ 5,194stars on GitHubPythonApache-2.0

Claude Code, Cursor, Codex or VS Code. No key. You approve one sign-in in your browser.

Repowise maps public repos from their source. Not affiliated with interplains. What is Repowise?

github.com/interplains/zero-breach-toolkitIndexed at 10ceaba

What is zero-breach-toolkit?

zero-breach-toolkit is a local triage engine for checking computers, Android phones and iPhone backups for traces of known mercenary spyware such as Pegasus, Predator, Graphite and Candiru. It checks browser profiles, installed apps, files and phone collections against published spyware indicator lists and writes a report of what matched and what could not be checked. The project is written in Python.

Written by a model from the README and the source, like the other summaries and answers on this page

266 files and 3,658 symbols in 3 modules, led by Python (214 files) and Shell (1).

Getting started with zero-breach-toolkit

  1. Install Python 3.8 or newer and open a terminal in the toolkit folder, then run every command from that folder.
  2. Recommended: download the latest indicator lists. This is the only step that uses the internet.
    python -X utf8 scan/zero-breach-toolkit.py --update
  3. Close your browsers and chat apps, then run the standard check of this computer.
    python -X utf8 scan/zero-breach-toolkit.py
  4. Run a check of a phone collection or backup folder.
    python -X utf8 scan/zero-breach-toolkit.py --phone "FOLDER"

Commands copied from the README

Releases on GitHub (latest v3.0.2, Nov 14, 2026)

Explore zero-breach-toolkit

Ask about this code in your agent

This connects Repowise to zero-breach-toolkit's code. It does not install zero-breach-toolkit. To install zero-breach-toolkit, use the install steps.

Useful if you want to change or fork zero-breach-toolkit: your agent can ask how it is put together and get answers that cite its files.

Ask about zero-breach-toolkit

Answers come from zero-breach-toolkit's README and source, with the files they cite. Two free answers a day without an account.

Want this for your own codebase? Map your repo free

About this page

Get a page like this for your own codebase

Repowise built this map of interplains/zero-breach-toolkit from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Free for 2 public repos, with a page like this one. No card. See how Repowise works

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub

interplains/zero-breach-toolkit FAQ

What is zero-breach-toolkit?

zero-breach-toolkit is a free, open-source check for traces of known mercenary spyware on computers, Android phones and iPhone backups. It reports what matched, how strong the evidence is and what could not be checked.

How does zero-breach-toolkit work?

zero-breach-toolkit compares browser profiles, installed apps, files and phone collections with published spyware indicator lists. It then writes a verdict of either no known indicators found or something matched, with the unchecked places listed.

How do I install zero-breach-toolkit?

zero-breach-toolkit runs from source with Python 3.8 or newer and needs no administrator rights or extra packages. Open a terminal in the toolkit folder and run python -X utf8 scan/zero-breach-toolkit.py. See the install steps

What language is zero-breach-toolkit written in?

zero-breach-toolkit is written in Python. Nearly all of its source files are Python files, with one shell script.

How is the zero-breach-toolkit code organized?

zero-breach-toolkit keeps its checking code in the scan directory, where the zbtriage package holds the entry points. The build directory packages the toolkit into one script and writes the indicator exports, and the tools directory holds release helper scripts.

When should I use zero-breach-toolkit?

Use zero-breach-toolkit to check a computer, Android phone or iPhone backup for traces of published mercenary spyware indicators. A match means look closer, not that the device is infected.

What license does zero-breach-toolkit use?

zero-breach-toolkit is licensed under Apache-2.0. The license identifier is given in the project's metadata.

Code health

6.6out of 10Fair

Hotspots average 3.2, the place fixes pay off most.

On the leaderboards:#48 of 71 Python repos

Key features of zero-breach-toolkit

  • Checks computers, Android phones and iPhone backups for traces of known mercenary spyware such as Pegasus, Predator, Graphite and Candiru.
  • Read-only: it does not modify source evidence or system settings and writes only temporary database snapshots and the reports you request.
  • Makes no network requests during a scan and has no upload feature.
  • Every report states what was found, how strong the evidence is and what could not be checked.
  • Includes a training example mode with made-up data so people can learn to read a report before a real check.

How interplains/zero-breach-toolkit works

Input enters through the command line, where scan/zbtriage/__main__.py and scan/zbtriage/cli.py act as the entry points and cli.py parses options such as the phone folder and report file paths. The scan directory holds the core checking code, which reads local collections such as phone log exports, databases, copied files and live Windows records. scan/zbtriage/report.py is one of the central files involved in producing the output. The result is a verdict of either no known indicators found or something matched, together with the list of places that could not be checked. The build directory turns the indicator lists into a denylist, a MISP export and a STIX export, and build/bundle.py packages the toolkit into one runnable script. The tools directory contains helper scripts for release checks and test fixtures.

The codebase has 266 files and 3,658 symbols in 3 modules, led by Python and Shell. Code health is 6.6 out of 10, rated fair.