zelcore

maintainer jfamousket · 1 votes · scanned 2026-08-03 00:08:14.047287

MEDIUM

Why flagged The PKGBUILD downloads a prebuilt binary tarball (an Electron app) from zelcore.io using a URL with non-deterministic query parameters (timestamp, nonce, force-download flags). While zelcore.io is the official project domain, the URL structure is a download-manager redirect rather than a stable, versioned artifact URL. The sha256sum is present and pinned, which mitigates silent substitution risk somewhat. However: (1) the binary is a prebuilt Electron application executed directly on the user's system with no source build, (2) the URL parameters suggest a download-manager system that could serve different content at different times despite the same URL, and (3) the package was generated by debtap from a Debian package rather than built from source. The sha256 checksum provides the primary integrity guarantee, but the non-deterministic URL means the checksum could become stale or mismatched without clear indication. This is a legitimate supply-chain concern for an executed binary from a non-standard download URL, warranting a MEDIUM rating.

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:15 source_x86_64=("$pkgname-$pkgver.tar.gz::https://zelcore.io/download/zelcore-for-linux-debian/?tmstv=1711476423&dlm-dp-dl-force=1&dlm-dp-dl-nonce=feb2949898")

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 binary tarball (an Electron app) from zelcore.io using a URL with non-deterministic query parameters (timestamp, nonce, force-download flags). While zelcore.io is the official project domain, the URL structure is a download-manager redirect rather than a stable, versioned artifact URL. The sha256sum is present and pinned, which mitigates silent substitution risk somewhat. However: (1) the binary is a prebuilt Electron application executed directly on the user's system with no source build, (2) the URL parameters suggest a download-manager system that could serve different content at different times despite the same URL, and (3) the package was generated by debtap from a Debian package rather than built from source. The sha256 checksum provides the primary integrity guarantee, but the non-deterministic URL means the checksum could become stale or mismatched without clear indication. This is a legitimate supply-chain concern for an executed binary from a non-standard download URL, warranting a MEDIUM rating.

PKGBUILD

1 offending line(s) highlighted

      1# Generated by debtap
    
      2# Maintainer: Famous
    
      3# Contributor: Famous
    
      4pkgname=zelcore
    
      5pkgver=7.13.3
    
      6pkgrel=0
    
      7pkgdesc="Zelcore Platform"
    
      8arch=('x86_64')
    
      9url="https://zelcore.io/"
    
      10license=('custom')
    
      11depends=('gtk3' 'libnotify' 'nss' 'libxss' 'libxtst' 'xdg-utils' 'at-spi2-core' 'util-linux-libs' 'libsecret')
    
      12optdepends=('libappindicator-gtk3')
    
      13options=('!strip' '!emptydirs')
    
      14install=${pkgname}.install
    
      15source_x86_64=("$pkgname-$pkgver.tar.gz::https://zelcore.io/download/zelcore-for-linux-debian/?tmstv=1711476423&dlm-dp-dl-force=1&dlm-dp-dl-nonce=feb2949898")
    
      16sha256sums_x86_64=('bf01ae5e6b6565a7ad8efb213e40403455b0373ca3e78e59a72ec160025e7dc2')
    
      17
    
      18
    
      19
    
      20package(){
    
      21
    
      22	# Extract package data
    
      23	tar xf data.tar.xz -C "${pkgdir}"
    
      24
    
      25	install -D -m644 "${pkgdir}/opt/ZelCore/LICENSES.chromium.html" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
    
      26
    
      27}
    
      28

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