tbdel

maintainer mahdium · 0 votes · scanned 2026-08-03 00:08:14.047287
MEDIUM
View on AUR ↗
Why flagged The PKGBUILD downloads and installs a prebuilt x86_64 binary from a personal/self-hosted Gitea instance (git.mahdium.ir) maintained by the package author. This is not an official distribution channel like GitHub, GitLab, or a distro mirror — it is a personal server that could be compromised, taken down, or silently replaced. The binary is executed directly on the user's system (installed to /usr/bin/tbdel). A sha256 checksum is present, which provides integrity verification against the specific downloaded artifact, but does not protect against the upstream host serving a malicious binary in the first place (the checksum would simply be updated). There is no source code build from a verifiable VCS, no reproducible build, and no third-party attestation. This is a classic supply-chain concern: a prebuilt binary from an unofficial personal host. The risk is real but not evidence of active malice, so MEDIUM is the correct rating.

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:11 source_x86_64=("https://git.mahdium.ir/mahdium/TBDel/releases/download/v${pkgver}/tbdel-v${pkgver}-linux-64.tar.xz")
MEDIUM AI review llm_review

An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 82%): The PKGBUILD downloads and installs a prebuilt x86_64 binary from a personal/self-hosted Gitea instance (git.mahdium.ir) maintained by the package author. This is not an official distribution channel like GitHub, GitLab, or a distro mirror — it is a personal server that could be compromised, taken down, or silently replaced. The binary is executed directly on the user's system (installed to /usr/bin/tbdel). A sha256 checksum is present, which provides integrity verification against the specific downloaded artifact, but does not protect against the upstream host serving a malicious binary in the first place (the checksum would simply be updated). There is no source code build from a verifiable VCS, no reproducible build, and no third-party attestation. This is a classic supply-chain concern: a prebuilt binary from an unofficial personal host. The risk is real but not evidence of active malice, so MEDIUM is the correct rating.

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: Mohammad Mahdi <me@mahdium.ir>
2pkgname=tbdel
3pkgver=3
4pkgrel=1
5pkgdesc="A simple command-line tool for managing a list of files and directories marked for deletion. User can add, remove, list, and execute the deletion of these entries."
6url="https://git.mahdium.ir/mahdium/TBDel"
7license=('AGPL3')
8arch=('x86_64')
9provides=("tbdel=$pkgver")
10
11source_x86_64=("https://git.mahdium.ir/mahdium/TBDel/releases/download/v${pkgver}/tbdel-v${pkgver}-linux-64.tar.xz")
12sha256sums_x86_64=(f3de937bbe41e5c1110bb003b64bf986fb075cf8ee8656eb4c3914bab59f3a9a)
13
14package() {
15 cd "$srcdir"
16 install -D tbdel-v${pkgver}-linux-64 "$pkgdir/usr/bin/tbdel"
17}
18

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