zero-breach-toolkit

LOW
maintainer VVS 0 votes scanned 2026-10-29 17:53:05.425985
View on AUR
Why flagged

Uploaded within the last 14 days with 2 or fewer community votes — little peer review so far.

Triggered rules

Low Few votes, recently uploaded zero_votes_recent

Uploaded within the last 14 days with 2 or fewer community votes — little peer review so far.

PKGBUILD

1# Maintainer: Vitaliy VVS Star <vitaliy <dot> star <at> Gmail-DOT-Com>
2
3pkgname=zero-breach-toolkit
4pkgver=0.1.11
5pkgrel=1
6pkgdesc="Offline spyware-triage scanner: checks local device traces against published mercenary-spyware IOC feeds"
7arch=('any')
8url="https://github.com/interplains/Zero-Breach-Toolkit"
9license=('Apache-2.0')
10depends=('python')
11optdepends=('android-tools: adb access for Android acquisition (AndroidQF workflow)'
12 'python-cryptography: decrypt encrypted iPhone backups')
13source=("${pkgname}.py::${url}/releases/download/v${pkgver}/${pkgname}.py")
14sha256sums=('91254ab664f343f66a5116074f766ed48db732e7ebbcbeab082e41a60a46912d')
15
16# Security notes (audit 2026-10-29):
17# - The pinned sha256sum above locks the exact release artifact that was
18# security-audited byte-for-byte. Upstream also GPG-signs releases with key
19# C24EC92B12D6670A2516065F9B4D575499AFA53C (self-published; see upstream
20# docs/VERIFYING.md) - verify out-of-band if you rely on attribution.
21# - The tool is offline by design: scans perform no network I/O, it writes
22# only under ~/.cache/zero-breach-triage and user directories.
23# - Upstream releases frequently; bump pkgver ONLY after re-reviewing the
24# new release diff, and update sha256sums from the signed SHA256SUMS.txt.
25
26package() {
27 install -Dm755 "${pkgname}.py" "${pkgdir}/usr/bin/${pkgname}"
28}
29
30# vim: ts=2 sw=2 et:
31

Scan history

Scanned at (UTC)SeverityRules
2026-10-29 17:53:05 Low 1

Report a package

Reports go to the AURWatch maintainer (one person) and are read by hand. No login required.

0 / 4000
Your suggestion