buttercup

MEDIUM
maintainer Wraient 0 votes scanned 2026-09-17 00:27:14.276658
View on AUR
Why flagged

This PKGBUILD has two real but non-malicious concerns: (1) It downloads a precompiled binary from GitHub releases with sha256sums='SKIP', meaning no integrity verification of the binary being installed to /usr/bin. The binary is from a small personal project (Wraient/buttercup) with no checksum pinning. (2) The build() step runs 'npm install -g webtorrent-cli' which installs an npm package globally into the system (outside $pkgdir), bypassing pacman's package management entirely. webtorrent-cli is a legitimate well-known package, but installing it globally via npm in build() is non-standard and leaves untracked files on the system. Neither pattern constitutes active malware/RCE/exfiltration, but the combination of an unverified binary + a global npm install that escapes pacman's control is a genuine medium-severity packaging concern. The pkgver() function also fetches from the GitHub API at build time, which is unusual but not malicious.

Triggered rules

Medium npm/yarn/pnpm install of an undeclared external package npm_install_external

Runs `npm/yarn/pnpm install <package>` for a package not in source=(), pulling unpinned, unreviewed code at build time. Severity downgraded: the package declares/looks like a Node.js consumer, where build-time installs are expected.

  • PKGBUILD:22 npm install -g webtorrent-cli
Medium AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 82%): This PKGBUILD has two real but non-malicious concerns: (1) It downloads a precompiled binary from GitHub releases with sha256sums='SKIP', meaning no integrity verification of the binary being installed to /usr/bin. The binary is from a small personal project (Wraient/buttercup) with no checksum pinning. (2) The build() step runs 'npm install -g webtorrent-cli' which installs an npm package globally into the system (outside $pkgdir), bypassing pacman's package management entirely. webtorrent-cli is a legitimate well-known package, but installing it globally via npm in build() is non-standard and leaves untracked files on the system. Neither pattern constitutes active malware/RCE/exfiltration, but the combination of an unverified binary + a global npm install that escapes pacman's control is a genuine medium-severity packaging concern. The pkgver() function also fetches from the GitHub API at build time, which is unusual but not malicious.

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: Wraient <rushikeshwastaken@gmail.com>
2pkgname='buttercup'
3pkgver=1.1.0
4pkgrel=2
5pkgdesc="Watch TV Shows / Movies from torrent."
6arch=("x86_64")
7url="https://github.com/Wraient/buttercup"
8license=('GPL')
9depends=('mpv' 'rofi' 'npm')
10source=("buttercup::https://github.com/Wraient/buttercup/releases/latest/download/buttercup")
11sha256sums=('SKIP')
12
13pkgver() {
14 # Fetch the latest release tag from GitHub and set it as pkgver
15 local latest_release
16 latest_release=$(curl -s https://api.github.com/repos/Wraient/buttercup/releases/latest | grep -Po '"tag_name": "\K.*?(?=")')
17 echo "${latest_release#v}"
18}
19
20build() {
21 # Install webtorrent-cli globally via npm
22 npm install -g webtorrent-cli
23}
24
25package() {
26 # Install the precompiled binary into /usr/bin
27 install -Dm755 "$srcdir/buttercup" "$pkgdir/usr/bin/buttercup"
28}
29

Scan history

Scanned at (UTC)SeverityRules
2026-09-17 00:27:14 Medium 2
2026-09-16 00:03:17 Medium 2
2026-09-15 00:25:31 Medium 2
2026-09-14 00:27:57 Medium 2
2026-09-13 00:19:54 Medium 2
2026-09-12 00:25:17 Medium 2
2026-09-11 00:19:22 Medium 2
2026-09-10 00:22:44 Medium 2
2026-09-09 00:04:09 Medium 2
2026-09-08 00:18:08 Medium 2
2026-09-07 00:30:15 Medium 2
2026-09-06 00:17:06 Medium 2
2026-09-05 00:16:27 Medium 2
2026-09-04 00:03:13 Medium 2
2026-09-03 00:15:47 Medium 2
2026-09-02 00:02:31 Medium 2
2026-09-01 00:11:19 Medium 2
2026-08-31 00:19:57 Medium 2
2026-08-30 00:04:14 Medium 2
2026-08-29 00:29:17 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