tamtam
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:11
source=("${pkgname}-${pkgver}.deb::https://desktop.tamtam.chat/v${pkgver}/TamTam-amd64.deb")
llm_review
An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The PKGBUILD downloads a prebuilt binary .deb from desktop.tamtam.chat, which is the official TamTam messenger distribution host (TamTam is a Russian messaging service by Mail.ru Group). The source is a closed-source prebuilt binary extracted and installed directly into the system, with a sha256sum check providing integrity verification against tampering in transit. The concern is real but typical for AUR packages wrapping proprietary messenger binaries: the binary is executed code from a vendor-controlled but non-open-source host, and users must trust the vendor. There is no obfuscation, no unofficial/personal host (this is the vendor's own distribution endpoint), and the checksum is present. This is a standard pattern for proprietary app AUR packages (similar to Slack, Zoom, Teams, etc.). The medium rating is appropriate because it is a closed-source prebuilt binary from a vendor host, not because of any active attack indicator.
PKGBUILD
1 offending line(s) highlighted# Maintainer: Vadim Tsesko <incubos at yandex dot com>
pkgname=tamtam
pkgver=1.4.15
pkgrel=1
pkgdesc='TamTam messenger for linux'
arch=('x86_64')
url='https://desktop.tamtam.chat/latest/'
license=('custom')
depends=('alsa-lib' 'gtk3' 'libsecret' 'libxss' 'libxtst' 'nss')
source=("${pkgname}-${pkgver}.deb::https://desktop.tamtam.chat/v${pkgver}/TamTam-amd64.deb")
sha256sums=('17b546ecd84074fbd8e7cf57a560cbf1f2c76228599776c9b998d706de86f088')
package() {
cd "${srcdir}"
tar -xJC "${pkgdir}" -f data.tar.xz
mkdir "${pkgdir}/usr/bin"
ln -s "/opt/TamTam/${pkgname}" "${pkgdir}/usr/bin/${pkgname}"
}
Scan history
| Scanned at (UTC) | Severity | Rules |
|---|---|---|
| 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 |