werf-bin

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

The PKGBUILD downloads a prebuilt binary from tuf.werf.io, which is the official TUF (The Update Framework) distribution endpoint for the werf project (werf.io is the official project site). TUF is a security framework specifically designed for secure software distribution, so this is actually the official, security-hardened release channel rather than a random personal host. However, it is still a prebuilt binary being installed directly to /usr/bin without source compilation, and the host tuf.werf.io, while official, is not a widely recognized platform like GitHub releases. A sha256sum is provided. The medium rating is borderline — this is the official vendor distribution mechanism — but since it installs an unauditable prebuilt binary directly to the system, the supply-chain concern is real if the host were compromised, and the binary cannot be verified beyond the single checksum. This is a common AUR pattern for -bin packages from official vendor hosts, making it closer to clean/low, but the non-GitHub/non-standard host and direct binary execution keep it at medium.

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:13 source=("https://tuf.werf.io/targets/releases/${pkgver}/linux-amd64/bin/werf")
Medium AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 80%): The PKGBUILD downloads a prebuilt binary from tuf.werf.io, which is the official TUF (The Update Framework) distribution endpoint for the werf project (werf.io is the official project site). TUF is a security framework specifically designed for secure software distribution, so this is actually the official, security-hardened release channel rather than a random personal host. However, it is still a prebuilt binary being installed directly to /usr/bin without source compilation, and the host tuf.werf.io, while official, is not a widely recognized platform like GitHub releases. A sha256sum is provided. The medium rating is borderline — this is the official vendor distribution mechanism — but since it installs an unauditable prebuilt binary directly to the system, the supply-chain concern is real if the host were compromised, and the binary cannot be verified beyond the single checksum. This is a common AUR pattern for -bin packages from official vendor hosts, making it closer to clean/low, but the non-GitHub/non-standard host and direct binary execution keep it at medium.

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: Roman Geraskin <roman dot n dot geraskin at gmail dot com>
2
3pkgname=werf-bin
4pkgver=2.6.4
5pkgrel=1
6pkgdesc='Kubernetes build and delivery tool'
7arch=('x86_64')
8url="https://werf.io"
9depends=('docker' 'git')
10license=('Apache')
11provides=('werf')
12conflicts=("werf-git")
13source=("https://tuf.werf.io/targets/releases/${pkgver}/linux-amd64/bin/werf")
14sha256sums=('e5fbbf13456cdeab90756e7cdc838f3a28b5fc6c159067faa40407fb81087c1a')
15
16package() {
17 install -Dm755 werf "${pkgdir}/usr/bin/werf"
18}
19# vim:set ts=2 sw=2 et:
20

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