elasticmq
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
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")
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# Maintainer: Sergey Mezentsev <thebits@yandex.ru>
pkgname=elasticmq
pkgver=1.7.1
pkgrel=1
pkgdesc="Amazon SQS compatible in-memory message queue"
arch=('any')
url="https://github.com/softwaremill/elasticmq"
license=("Apache-2.0")
depends=("java-runtime-headless")
source=("https://s3-eu-west-1.amazonaws.com/softwaremill-public/elasticmq-server-${pkgver}.jar")
noextract=("elasticmq-server-${pkgver}.jar")
sha256sums=('a40dfd03fd8e2f17418f3c61a460c1daea902119145bdce97d09a81f03aa0428')
package() {
cd "${srcdir}"
install -D -m755 "elasticmq-server-${pkgver}.jar" "${pkgdir}/usr/bin/elasticmq"
}
Scan history
| Scanned at (UTC) | Severity | Rules |
|---|---|---|
| 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 |