jprq

maintainer pro_username · 0 votes · scanned 2026-08-03 00:08:14.047287
MEDIUM
View on AUR ↗
Why flagged The PKGBUILD downloads a prebuilt binary from a legitimate GitHub releases URL (azimjohn/jprq, a real open-source project). There is no obfuscation, no encoded payload, no exfiltration, and no active source substitution. However, there are genuine concerns: (1) no checksums/integrity verification (no sha256sums, no source= array with hashes), meaning a compromised release asset or MITM could deliver a malicious binary undetected; (2) the binary is downloaded at build time rather than declared in the source array, bypassing makepkg's integrity checking entirely; (3) the case statement has duplicate 'Darwin $CARCH' entries and the architecture matching is broken (CARCH is an Arch Linux variable, not an architecture string like 'x86_64', so the Linux cases will never match correctly). These are real packaging quality and security concerns but not an active attack — the source is a known public GitHub project with a legitimate release. This rates as medium risk due to the missing integrity verification of an executed binary, not high.

Triggered rules

MEDIUM AI review downgraded a static finding llm_review

The static rules flagged this HIGH, but an AI model (anthropic/claude-4.6-sonnet-20260217) reviewed the full PKGBUILD and judged it MEDIUM (confidence 85%): The PKGBUILD downloads a prebuilt binary from a legitimate GitHub releases URL (azimjohn/jprq, a real open-source project). There is no obfuscation, no encoded payload, no exfiltration, and no active source substitution. However, there are genuine concerns: (1) no checksums/integrity verification (no sha256sums, no source= array with hashes), meaning a compromised release asset or MITM could deliver a malicious binary undetected; (2) the binary is downloaded at build time rather than declared in the source array, bypassing makepkg's integrity checking entirely; (3) the case statement has duplicate 'Darwin $CARCH' entries and the architecture matching is broken (CARCH is an Arch Linux variable, not an architecture string like 'x86_64', so the Linux cases will never match correctly). These are real packaging quality and security concerns but not an active attack — the source is a known public GitHub project with a legitimate release. This rates as medium risk due to the missing integrity verification of an executed binary, not high.

1 higher static finding superseded - not the current verdict (shown for transparency)
HIGH Downloaded file is executed download_then_exec

A file fetched with curl/wget (not part of source=(), so never checksum-verified) is later made executable or run — a fetch-and-execute pattern split across statements.

  • PKGBUILD:35 install -Dm755 ./jprq "$pkgdir/usr/bin/jprq"

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: Davron <xamdamovdavron6@gmail.com>
2pkgname='jprq'
3pkgver=2.3
4pkgrel=1
5epoch=
6pkgdesc="This is a free and open tool for exposing local servers to public network (the internet)"
7arch=('any')
8makedepends=("curl")
9license=('MIT')
10url="https://github.com/azimjohn/jprq/releases/download/2.3"
11
12build() {
13 set -e
14
15 URL_PREFIX="https://github.com/azimjohn/jprq/releases/download/2.3"
16
17 case "$(uname -sm)" in
18 "Darwin $CARCH") FILENAME="jprq-darwin-amd64" ;;
19 "Darwin $CARCH") FILENAME="jprq-darwin-arm64" ;;
20 "Linux $CARCH") FILENAME="jprq-linux-amd64" ;;
21 "Linux $CARCH") FILENAME="jprq-linux-386" ;;
22 *) echo "Unsupported architecture: $(uname -sm)" >&2; exit 1 ;;
23 esac
24
25 echo "Downloading $FILENAME from github releases"
26 if ! curl -sSLf "$URL_PREFIX/$FILENAME" -o "jprq"; then
27 echo "Failed to write to $INSTALL_DIR; try with sudo" >&2
28 exit 1
29 fi
30
31 echo "jprq is successfully installed"
32}
33
34package() {
35 install -Dm755 ./jprq "$pkgdir/usr/bin/jprq"
36}
37

Scan history

Scanned at (UTC)SeverityRules
2026-08-03 00:08:14 MEDIUM 2
2026-08-02 00:16:08 MEDIUM 2
2026-08-01 00:11:18 MEDIUM 2
2026-07-31 00:14:10 MEDIUM 2
2026-07-30 00:17:23 MEDIUM 2
2026-07-29 00:25:53 MEDIUM 2
2026-07-28 00:07:28 MEDIUM 2
2026-07-27 00:24:32 MEDIUM 2
2026-07-26 00:07:32 MEDIUM 2
2026-07-25 00:13:44 MEDIUM 2
2026-07-24 00:02:28 MEDIUM 2
2026-07-23 00:14:47 MEDIUM 2
2026-07-22 00:29:32 MEDIUM 2
2026-07-21 00:24:15 MEDIUM 2
2026-07-20 00:19:49 MEDIUM 2
2026-07-19 00:17:08 MEDIUM 2
2026-07-18 00:14:48 MEDIUM 2
2026-07-17 00:06:16 MEDIUM 2
2026-07-16 00:05:41 MEDIUM 2
2026-07-15 00:09:25 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