elasticmq

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

The PKGBUILD downloads a prebuilt JAR file (executable JVM bytecode) from an S3 bucket (softwaremill-public on AWS eu-west-1) rather than building from source. While this S3 bucket is the official distribution channel used by SoftwareMill for elasticmq releases (consistent with the upstream GitHub repo at github.com/softwaremill/elasticmq), it is still an S3 bucket rather than a GitHub release asset, meaning there is no cryptographic provenance tied to a GitHub release. The JAR is installed directly as an executable. A sha256sum is provided, which mitigates substitution risk somewhat, but the hash only protects against accidental corruption or a swap after the PKGBUILD was written — it does not verify the JAR's authenticity or signing. The core concern is a prebuilt binary from a cloud storage bucket with no GPG/sigstore verification. This is a real but low-probability supply-chain risk: medium severity is appropriate.

Triggered rules

Medium source=() URL on a non-standard host source_untrusted_domain

One or more source=() URLs point to a host outside the trusted allowlist (github.com, gitlab.com, codeberg.org, pypi.org, …).

  • PKGBUILD:10 source=("https://s3-eu-west-1.amazonaws.com/softwaremill-public/elasticmq-server-${pkgver}.jar")
Medium AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 78%): The PKGBUILD downloads a prebuilt JAR file (executable JVM bytecode) from an S3 bucket (softwaremill-public on AWS eu-west-1) rather than building from source. While this S3 bucket is the official distribution channel used by SoftwareMill for elasticmq releases (consistent with the upstream GitHub repo at github.com/softwaremill/elasticmq), it is still an S3 bucket rather than a GitHub release asset, meaning there is no cryptographic provenance tied to a GitHub release. The JAR is installed directly as an executable. A sha256sum is provided, which mitigates substitution risk somewhat, but the hash only protects against accidental corruption or a swap after the PKGBUILD was written — it does not verify the JAR's authenticity or signing. The core concern is a prebuilt binary from a cloud storage bucket with no GPG/sigstore verification. This is a real but low-probability supply-chain risk: medium severity is appropriate.

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: Sergey Mezentsev <thebits@yandex.ru>
2pkgname=elasticmq
3pkgver=1.7.1
4pkgrel=1
5pkgdesc="Amazon SQS compatible in-memory message queue"
6arch=('any')
7url="https://github.com/softwaremill/elasticmq"
8license=("Apache-2.0")
9depends=("java-runtime-headless")
10source=("https://s3-eu-west-1.amazonaws.com/softwaremill-public/elasticmq-server-${pkgver}.jar")
11noextract=("elasticmq-server-${pkgver}.jar")
12sha256sums=('a40dfd03fd8e2f17418f3c61a460c1daea902119145bdce97d09a81f03aa0428')
13
14package() {
15 cd "${srcdir}"
16 install -D -m755 "elasticmq-server-${pkgver}.jar" "${pkgdir}/usr/bin/elasticmq"
17}
18

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