marmota
The PKGBUILD downloads and installs a prebuilt binary .deb package from download.marmota.app, which is the official vendor download host for the Marmota application. The binary is an Electron-based app (gtk3/nss/libxss deps confirm this) and is extracted directly into pkgdir, meaning whatever is in that .deb gets installed and executed on the user's system. A b2sum checksum is provided, which pins the specific artifact. The host appears to be the legitimate upstream distribution channel for this proprietary application. This is a standard pattern for AUR packages wrapping proprietary software distributed as .deb files (similar to slack, discord, zoom, etc.). The risk is the standard supply-chain concern of trusting a single vendor-controlled binary host with no reproducibility — if the vendor's server is compromised or the vendor pushes a malicious update, the checksum would need to be updated to catch it, but the current pinned checksum does provide integrity for the specific version. This is a genuine medium-severity concern (executed binary from a single vendor host) but not an active attack or clearly malicious pattern.
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=("https://download.marmota.app/linux/deb/x64/${pkgname}_${pkgver}_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 and installs a prebuilt binary .deb package from download.marmota.app, which is the official vendor download host for the Marmota application. The binary is an Electron-based app (gtk3/nss/libxss deps confirm this) and is extracted directly into pkgdir, meaning whatever is in that .deb gets installed and executed on the user's system. A b2sum checksum is provided, which pins the specific artifact. The host appears to be the legitimate upstream distribution channel for this proprietary application. This is a standard pattern for AUR packages wrapping proprietary software distributed as .deb files (similar to slack, discord, zoom, etc.). The risk is the standard supply-chain concern of trusting a single vendor-controlled binary host with no reproducibility — if the vendor's server is compromised or the vendor pushes a malicious update, the checksum would need to be updated to catch it, but the current pinned checksum does provide integrity for the specific version. This is a genuine medium-severity concern (executed binary from a single vendor host) but not an active attack or clearly malicious pattern.
PKGBUILD
1 offending line(s) highlighted# Maintainer: "bountin" Martin Prebio
pkgname=marmota
pkgver=22.17.0
pkgrel=1
pkgdesc="Simple Markdown Presentations"
arch=('x86_64')
url=https://marmota.app/downloads/thank-you/#linux
licence=('unknown')
depends=("gtk3" "libxss" "libxtst" "nss")
source=("https://download.marmota.app/linux/deb/x64/${pkgname}_${pkgver}_amd64.deb")
noextract=("${pkgname}_${pkgver}_amd64.deb")
b2sums=('190afa970dcc419ce6bca12f6cad7c557389aaa9d90f3999a473be316fce4bd73a9eff1eb0fc6e6399f9fecba8241866ddbe168d4692ad79a34130117f79c575')
package() {
bsdtar -O -xf "${pkgname}_${pkgver}_amd64.deb" data.tar.xz | bsdtar -C "${pkgdir}" -xJf -
# Permissions fix
find "${pkgdir}" -type d -exec chmod 755 {} \;
# Move license
# install -dm755 "${pkgdir}/usr/share/licenses/${pkgname}"
# mv "${pkgdir}/usr/share/${pkgname}/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}"
# ln -s "/usr/share/licenses/${pkgname}/LICENSE" "${pkgdir}/usr/share/${pkgname}/LICENSE"
}
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 |