buttercup

MEDIUM
maintainer Wraient 0 votes scanned 2026-11-01 00:21:48.120785
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-11-01 00:21:48 Medium 2
2026-10-31 00:07:41 Medium 2
2026-10-30 00:29:30 Medium 2
2026-10-29 00:13:55 Medium 2
2026-10-28 00:06:54 Medium 2
2026-10-27 00:23:28 Medium 2
2026-10-26 00:12:40 Medium 2
2026-10-25 00:20:48 Medium 2
2026-10-24 00:14:55 Medium 2
2026-10-23 00:02:19 Medium 2
2026-10-22 00:13:10 Medium 2
2026-10-21 00:12:50 Medium 2
2026-10-20 00:10:31 Medium 2
2026-10-19 00:03:55 Medium 2
2026-10-18 00:06:55 Medium 2
2026-10-17 00:21:55 Medium 2
2026-10-16 00:12:47 Medium 2
2026-10-15 00:28:05 Medium 2
2026-10-14 00:06:47 Medium 2
2026-10-13 00:23:45 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