desktime
The source URL 'https://desktime.com/updates/electron/linux?deb' is a query-parameter redirect endpoint rather than a versioned, stable artifact URL. This means the URL does not pin to a specific release — it resolves to whatever the server currently serves as 'latest'. The sha256sum provides a snapshot integrity check at packaging time, but if the upstream server silently rotates the binary (e.g. after a compromise or intentional swap), the checksum in the PKGBUILD would become stale and a future build without checksum verification could pull a different binary. More critically, the package() function runs 'bsdtar -xf data.tar.xz' without first extracting the .deb properly (missing the 'ar x' step to unpack the .deb into control.tar and data.tar.xz), suggesting the build may be broken or relies on a side-effect. The core concern is a prebuilt proprietary binary installed from a non-versioned endpoint — a real supply-chain risk for executed code, even though the domain is the official vendor domain. This is a genuine medium: not clearly malicious, but the floating URL pattern means the sha256 check is the only guard and future updates could silently change the binary.
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://desktime.com/updates/electron/linux?deb")
llm_review
An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): The source URL 'https://desktime.com/updates/electron/linux?deb' is a query-parameter redirect endpoint rather than a versioned, stable artifact URL. This means the URL does not pin to a specific release — it resolves to whatever the server currently serves as 'latest'. The sha256sum provides a snapshot integrity check at packaging time, but if the upstream server silently rotates the binary (e.g. after a compromise or intentional swap), the checksum in the PKGBUILD would become stale and a future build without checksum verification could pull a different binary. More critically, the package() function runs 'bsdtar -xf data.tar.xz' without first extracting the .deb properly (missing the 'ar x' step to unpack the .deb into control.tar and data.tar.xz), suggesting the build may be broken or relies on a side-effect. The core concern is a prebuilt proprietary binary installed from a non-versioned endpoint — a real supply-chain risk for executed code, even though the domain is the official vendor domain. This is a genuine medium: not clearly malicious, but the floating URL pattern means the sha256 check is the only guard and future updates could silently change the binary.
PKGBUILD
1 offending line(s) highlightedpkgname=desktime
pkgver=6.1.3
pkgrel=0
pkgdesc="Desktime client for Linux"
arch=('x86_64')
url="https://desktime.com"
license=(custom)
depends=(desktop-file-utils hicolor-icon-theme libappindicator-gtk2 libxss)
install=$pkgname.install
source=("$pkgname-$pkgver.deb::https://desktime.com/updates/electron/linux?deb")
sha256sums=('79fec9a56da8b0e07b8e34f91d0c9933d88451fdcc92e1f542be292702babd77')
package()
{
bsdtar -xf data.tar.xz -C "$pkgdir/"
}
# vim:et:sw=4:sts=4
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 |