alloyctl-bin

maintainer szymonwilczek · 0 votes · scanned 2026-08-03 00:08:14.047287
LOW
View on AUR ↗
Why flagged The package installs a prebuilt binary from the project's official GitHub releases, which is a normal practice for AUR packages; the low severity is due to limited votes and recent upload, not malicious content.

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.

LOW AI review llm_review

An AI model (qwen/qwen3-235b-a22b-2507) reviewed this and agrees it is LOW (confidence 95%): The package installs a prebuilt binary from the project's official GitHub releases, which is a normal practice for AUR packages; the low severity is due to limited votes and recent upload, not malicious content.

PKGBUILD

1# Maintainer: Szymon Wilczek <swilczek.lx@gmail.com>
2#
3# scripts/build-packages renders it into ready PKGBUILD by substituting
4# the version and the release tarball's SHA-256, so the checksum can
5# never disagree with the artifact it is published next to.
6#
7# 0.2.0 and 2a62877f1300ba27e2b1f2c65018e4da133c2b1460e4a793932ea0933e4cddcf are the only placeholders.
8pkgname=alloyctl-bin
9pkgver=0.2.0
10pkgrel=1
11pkgdesc="SteelSeries device configuration TUI for Linux (prebuilt binary)"
12arch=('x86_64')
13url="https://github.com/szymonwilczek/alloyctl"
14license=('GPL-2.0-only')
15depends=('ncurses')
16provides=('alloyctl')
17conflicts=('alloyctl')
18source=("https://github.com/szymonwilczek/alloyctl/releases/download/v${pkgver}/alloyctl-${pkgver}-linux-x86_64.tar.gz")
19sha256sums=('2a62877f1300ba27e2b1f2c65018e4da133c2b1460e4a793932ea0933e4cddcf')
20
21package() {
22 cd "alloyctl-${pkgver}-linux-x86_64"
23
24 install -Dm755 alloyctl "${pkgdir}/usr/bin/alloyctl"
25 install -Dm644 70-alloyctl-uinput.rules \
26 "${pkgdir}/usr/lib/udev/rules.d/70-alloyctl-uinput.rules"
27
28 # generate the per-device hidraw rule from the binary's own driver registry,
29 # matching what 'make install' and install.sh do
30 install -d "${pkgdir}/usr/lib/udev/rules.d"
31 ./alloyctl --dump-udev \
32 >"${pkgdir}/usr/lib/udev/rules.d/71-alloyctl-hidraw.rules"
33
34 install -Dm644 README.rst "${pkgdir}/usr/share/doc/${pkgname}/README.rst"
35 install -Dm644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
36}
37

Changes since previous scan

--- PKGBUILD @ 2026-07-24 00:02
+++ PKGBUILD @ 2026-08-03 00:08
@@ -4,9 +4,9 @@
# the version and the release tarball's SHA-256, so the checksum can
# never disagree with the artifact it is published next to.
#
-# 0.1.0 and be01a50881ae379ec9c8b8055a3f52bd4471a78cfc3a29f6c9c948b7686aaf80 are the only placeholders.
+# 0.2.0 and 2a62877f1300ba27e2b1f2c65018e4da133c2b1460e4a793932ea0933e4cddcf are the only placeholders.
pkgname=alloyctl-bin
-pkgver=0.1.0
+pkgver=0.2.0
pkgrel=1
pkgdesc="SteelSeries device configuration TUI for Linux (prebuilt binary)"
arch=('x86_64')
@@ -16,7 +16,7 @@
provides=('alloyctl')
conflicts=('alloyctl')
source=("https://github.com/szymonwilczek/alloyctl/releases/download/v${pkgver}/alloyctl-${pkgver}-linux-x86_64.tar.gz")
-sha256sums=('be01a50881ae379ec9c8b8055a3f52bd4471a78cfc3a29f6c9c948b7686aaf80')
+sha256sums=('2a62877f1300ba27e2b1f2c65018e4da133c2b1460e4a793932ea0933e4cddcf')
package() {
cd "alloyctl-${pkgver}-linux-x86_64"

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 00:17:23 LOW 2
2026-07-29 00:25:53 LOW 2
2026-07-28 00:07:28 LOW 2
2026-07-27 00:24:32 LOW 2
2026-07-26 00:07:32 LOW 2
2026-07-25 00:13:44 LOW 2
2026-07-24 01:26:42 LOW 2
2026-07-24 00:02:28 MEDIUM 2
2026-07-23 23:26:18 MEDIUM 2

Report a package

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

0 / 4000
Your suggestion