autoadb-git

maintainer vaclavmaly · 1 votes · scanned 2026-08-03 00:08:14.047287
LOW
View on AUR ↗
Why flagged The package builds from the project's own GitHub source, which is normal for AUR packages; the recent orphan/re-adopt cycle is a procedural flag but does not indicate malicious intent or supply-chain risk.

Triggered rules

LOW AI review downgraded a static finding llm_review

The static rules flagged this MEDIUM, but an AI model (qwen/qwen3-235b-a22b-2507) reviewed the full PKGBUILD and judged it LOW (confidence 95%): The package builds from the project's own GitHub source, which is normal for AUR packages; the recent orphan/re-adopt cycle is a procedural flag but does not indicate malicious intent or supply-chain risk.

1 higher static finding superseded - not the current verdict (shown for transparency)
MEDIUM Recently orphaned & re-adopted orphaned_readopted

This package was orphaned and re-adopted within the last 30 days — a window where ownership transfers can introduce malicious changes.

PKGBUILD

1# Contributor: Cullen Ross <cullenrss@gmail.com>
2
3_pkgname='autoadb'
4pkgname="${_pkgname}-git"
5pkgver=r4.7f84029
6pkgrel=4
7arch=('x86_64')
8license=('Apache-2.0')
9makedepends=('git' 'rust')
10provides=('autoadb')
11conflicts=('autoadb')
12pkgdesc="Allows executing a command whenever a new device is connected to adb"
13url="https://github.com/rom1v/${_pkgname}"
14source=("git+https://github.com/rom1v/autoadb")
15sha256sums=('SKIP')
16
17pkgver() {
18 cd "${_pkgname}"
19 printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
20}
21
22build() {
23 cd ${_pkgname}
24 cargo build --release
25}
26
27package() {
28 cd ${_pkgname}
29 install -D -m 755 "$srcdir/${_pkgname}/target/release/${_pkgname}" "${pkgdir}/usr/bin/${_pkgname}"
30}
31

Scan history

Scanned at (UTC)SeverityRules
2026-08-03 00:08:14 LOW 2
2026-08-02 00:16:08 LOW 2
2026-08-01 00:11:18 LOW 2
2026-07-31 00:14:10 LOW 2
2026-07-30 19:16:23 MEDIUM 1
2026-07-30 17:15:21 MEDIUM 1
2026-06-18 16:11:54 CLEAN 0

Report a package

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

0 / 4000
Your suggestion