replit-desktop-app

maintainer orphaned · 2 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged The PKGBUILD downloads a prebuilt .deb binary from desktop.replit.com (the official Replit desktop download endpoint) and extracts it directly into the package tree. While the domain is Replit's own, the source URL is a redirect/alias ('download/deb') rather than a versioned artifact URL, meaning the sha256sum check is the only integrity guard — if the upstream host serves a different binary for the same URL in the future, the checksum would catch it only if the maintainer updates the PKGBUILD. More importantly, the package installs a prebuilt Electron application binary blob from an external host rather than building from source, which is a genuine supply-chain concern: the binary is executed at runtime and its contents are not auditable from the PKGBUILD alone. The electron dependency is used as a system runtime but the app's own asar and native modules come from the deb. This is a real medium-severity supply-chain risk (prebuilt executed binary from an external host), not a false positive, though it is not clearly malicious.

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:16 replit.deb::https://desktop.replit.com/download/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 PKGBUILD downloads a prebuilt .deb binary from desktop.replit.com (the official Replit desktop download endpoint) and extracts it directly into the package tree. While the domain is Replit's own, the source URL is a redirect/alias ('download/deb') rather than a versioned artifact URL, meaning the sha256sum check is the only integrity guard — if the upstream host serves a different binary for the same URL in the future, the checksum would catch it only if the maintainer updates the PKGBUILD. More importantly, the package installs a prebuilt Electron application binary blob from an external host rather than building from source, which is a genuine supply-chain concern: the binary is executed at runtime and its contents are not auditable from the PKGBUILD alone. The electron dependency is used as a system runtime but the app's own asar and native modules come from the deb. This is a real medium-severity supply-chain risk (prebuilt executed binary from an external host), not a false positive, though it is not clearly malicious.

PKGBUILD

1 offending line(s) highlighted

      1# Maintainer: Kid <hi at xuann dot wang>
    
      2
    
      3pkgname=replit-desktop-app
    
      4pkgver=1.0.14
    
      5pkgrel=1
    
      6pkgdesc='The collaborative browser based IDE'
    
      7arch=(x86_64)
    
      8url=https://replit.com/desktop
    
      9license=(custom)
    
      10depends=(
    
      11	electron
    
      12)
    
      13install=.install
    
      14
    
      15source=(
    
      16	replit.deb::https://desktop.replit.com/download/deb
    
      17	replit
    
      18)
    
      19sha256sums=('04e2233d75a3f494bc0a3e15ec21119186c15c9f4df5bd5e5942a13d99165170'
    
      20            '9392ee9aced0cda3a50e00bc1fe40f75830388143254cbcb42929802b835d277')
    
      21
    
      22package() {
    
      23	local usr="$pkgdir/usr"
    
      24	local lib="$usr/lib/replit"
    
      25
    
      26	tar xf data.tar.zst -C "$pkgdir"
    
      27
    
      28	find "$lib" -type f ! -name '*.asar' -exec rm {} \;
    
      29	rm -d "$lib/locales"
    
      30	rm -r "$usr/share/lintian"
    
      31
    
      32	install -D replit -t "$usr/bin"
    
      33}
    
      34

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