werf-bin

maintainer rgeraskin · 1 votes · scanned 2026-08-03 00:08:14.047287
MEDIUM
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-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