| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| archivegenocide-signing-key.asc | 2026-10-29 | 421 Bytes | |
| SHA256SUMS.txt | 2026-10-29 | 187 Bytes | |
| SHA256SUMS.txt.asc | 2026-10-29 | 228 Bytes | |
| zero-breach-toolkit.py | 2026-10-29 | 973.6 kB | |
| zero-breach-toolkit.py.asc | 2026-10-29 | 228 Bytes | |
| README.md | 2026-10-29 | 1.2 kB | |
| Zero Breach Toolkit v0.1.13 source code.tar.gz | 2026-10-29 | 732.2 kB | |
| Zero Breach Toolkit v0.1.13 source code.zip | 2026-10-29 | 872.9 kB | |
| Totals: 8 Items | 2.6 MB | 13 | |
Zero Breach Toolkit 0.1.13.
What changed
- iPhone: if an encrypted backup can't be read because
cryptographyis missing, the message now names the Python running the check and gives the command that installs it there. The usual cause is that it was installed for a different Python on the same computer. - Program-file check: folders it could not open are counted separately from files it could not read, so a gap no longer says things like "3 of 1 candidate file(s)" (contributed in [#19]).
- Help: a simpler fix for "No such file or directory" on a Mac (drag the script into Terminal, from any folder),
python3in the backup install command, and a note that thethird_party/candirufolder holds detection rules, not spyware.
Full list in CHANGELOG.md (github.com).
Verify before running
zero-breach-toolkit.py SHA-256: bb0e6a7a36ee659c0494d02e9f7495d5fd4701f1ab7e57529e79925cb581ae15
Signed with key C24E C92B 12D6 670A 2516 065F 9B4D 5754 99AF A53C. See docs/VERIFYING.md (github.com).