desktime

MEDIUM
maintainer michalzuber 3 votes scanned 2026-09-17 00:27:14.276658
View on AUR
Why flagged

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

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=("$pkgname-$pkgver.deb::https://desktime.com/updates/electron/linux?deb")
Medium AI review 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) highlighted
1pkgname=desktime
2pkgver=6.1.3
3pkgrel=0
4pkgdesc="Desktime client for Linux"
5arch=('x86_64')
6url="https://desktime.com"
7license=(custom)
8depends=(desktop-file-utils hicolor-icon-theme libappindicator-gtk2 libxss)
9install=$pkgname.install
10
11source=("$pkgname-$pkgver.deb::https://desktime.com/updates/electron/linux?deb")
12sha256sums=('79fec9a56da8b0e07b8e34f91d0c9933d88451fdcc92e1f542be292702babd77')
13
14package()
15{
16 bsdtar -xf data.tar.xz -C "$pkgdir/"
17}
18
19# vim:et:sw=4:sts=4
20

Scan history

Scanned at (UTC)SeverityRules
2026-09-17 00:27:14 Medium 2
2026-09-16 00:03:17 Medium 2
2026-09-15 00:25:31 Medium 2
2026-09-14 00:27:57 Medium 2
2026-09-13 00:19:54 Medium 2
2026-09-12 00:25:17 Medium 2
2026-09-11 00:19:22 Medium 2
2026-09-10 00:22:44 Medium 2
2026-09-09 00:04:09 Medium 2
2026-09-08 00:18:08 Medium 2
2026-09-07 00:30:15 Medium 2
2026-09-06 00:17:06 Medium 2
2026-09-05 00:16:27 Medium 2
2026-09-04 00:03:13 Medium 2
2026-09-03 00:15:47 Medium 2
2026-09-02 00:02:31 Medium 2
2026-09-01 00:11:19 Medium 2
2026-08-31 00:19:57 Medium 2
2026-08-30 00:04:14 Medium 2
2026-08-29 00:29:17 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