Zero-Breach-Toolkit
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.
Runssource: GitHubPythonApache-2.0commit 465134c67953
Python, Apache-2.0 licensed.
Zero-Breach-Toolkit runs. An Argusic agent installed it in 0.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Zero Breach Toolkit 0.1.15 builds, installs, and runs: the CLI answers --version, --describe outputs valid JSON, a targeted scan on an empty directory produces a clean report (exit 3, correct), and the full test suite passes 1971/2025 tests with only platform-specific skips.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Missing optional cryptography dependency for encrypted iOS backup tests (84 tests skipped initially)0.3 minutes
- Install time
- under a minute
- Cold machine to finish
- 70 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- pytest tests/ -q --tb=no from scan/ dir: 1971 passed, 54 skipped (platform-conditioned only: Windows, POSIX FIFOs, sqlite3.setlimit), 1021 subtests passed, exit 0
- Model tokens used
- 228,239
- Exact commit tested
- 465134c67953
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc 'cd /work/repo/scan && /work/repo/venv/bin/python -m pytest tests/ -q --tb=no 2>&1 | ta… I have all the data from the complete runs. Let me compute the total elapsed and write the final re… From the earlier complete run: 1971 passed, 54 skipped, 1021 subtests passed, exit 0. The 54 skips … 2026-11-01T08:38:23.155630Z ERROR codex_core::session: failed to record rollout items: thread 01a19… 2026-11-01T08:38:23.155671Z ERROR codex_core::session: failed to record rollout items: thread 01a19… 2026-11-01T08:38:23.155680Z ERROR codex_core::session: failed to record rollout items: thread 01a19… 2026-11-01T08:38:23.155689Z ERROR codex_core::session: failed to record rollout items: thread 01a19… 2026-11-01T08:38:23.155704Z ERROR codex_core::session: failed to record rollout items: thread 01a19… tokens used 228,239 I have all the data from the complete runs. Let me compute the total elapsed and write the final re… From the earlier complete run: 1971 passed, 54 skipped, 1021 subtests passed, exit 0. The 54 skips …
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.5 minutes, faster than the median of the 46 comparable projects Argusic has measured.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 47 Python projects Argusic has installed and timed, Zero-Breach-Toolkit was the 8th fastest to reach a running state, and 27 of 47 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.5 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zero-breach-toolkit)Questions
- Does Zero-Breach-Toolkit run?
- Yes. Zero-Breach-Toolkit runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test Zero-Breach-Toolkit?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 465134c67953. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Zero-Breach-Toolkit?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Zero-Breach-Toolkit take to install?
- 0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does Zero-Breach-Toolkit need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Zero-Breach-Toolkit?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Zero-Breach-Toolkit compare with the alternatives?
- Of the 47 Python projects Argusic has installed and timed, Zero-Breach-Toolkit was the 8th fastest to reach a running state, and 27 of 47 reached one at all.
- Where is the evidence for Zero-Breach-Toolkit?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.