python-sentry_crashpad

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

The PKGBUILD installs a Python package directly from PyPI using pip without any source verification (no checksums, no source array, no integrity check). The package 'sentry_crashpad' is pulled from PyPI at build time, meaning whatever is currently published under that name/version on PyPI gets installed. While PyPI is a legitimate ecosystem mirror, this pattern bypasses Arch's normal source integrity mechanisms (no source=() array, no sha256sums). More importantly, sentry_crashpad is a C++ crash reporting library that ships pre-compiled native binaries inside the wheel — these are executed binaries from a third-party PyPI package maintained by 'EndstoneMC', not the official Sentry organization. The package URL points to a personal/project GitHub (EndstoneMC/sentry-crashpad), not the official getsentry/sentry-native upstream. Installing pre-compiled native binaries from an unofficial PyPI package without any integrity verification is a genuine supply-chain concern: if the PyPI package is compromised or typosquatted, arbitrary native code executes on the user's system. This is a real medium-severity supply-chain risk, not a false positive.

Triggered rules

Low pip install of an external package pip_install_external

`pip install <package>` fetches an unpinned package from PyPI at build time, outside source=() and makepkg's checksums. Severity reduced: python-* packages routinely use pip.

  • PKGBUILD:12 pip install --no-deps --target="sentry_crashpad" sentry_crashpad==0.7.17.1
Medium AI review of an ambiguous pattern llm_review

The static rules found a suspicious pattern they could not resolve, so an AI model (anthropic/claude-4.6-sonnet-20260217) reviewed it and judged it MEDIUM (confidence 82%): The PKGBUILD installs a Python package directly from PyPI using pip without any source verification (no checksums, no source array, no integrity check). The package 'sentry_crashpad' is pulled from PyPI at build time, meaning whatever is currently published under that name/version on PyPI gets installed. While PyPI is a legitimate ecosystem mirror, this pattern bypasses Arch's normal source integrity mechanisms (no source=() array, no sha256sums). More importantly, sentry_crashpad is a C++ crash reporting library that ships pre-compiled native binaries inside the wheel — these are executed binaries from a third-party PyPI package maintained by 'EndstoneMC', not the official Sentry organization. The package URL points to a personal/project GitHub (EndstoneMC/sentry-crashpad), not the official getsentry/sentry-native upstream. Installing pre-compiled native binaries from an unofficial PyPI package without any integrity verification is a genuine supply-chain concern: if the PyPI package is compromised or typosquatted, arbitrary native code executes on the user's system. This is a real medium-severity supply-chain risk, not a false positive.

PKGBUILD

1 offending line(s) highlighted
1# Maintainer: FTS427 <FTS427@outlook.com>
2# Python package author: Vincent <magicdroidx@gmail.com>
3pkgname=python-sentry_crashpad
4pkgver=0.7.17.1
5pkgrel=2
6pkgdesc="An open-source multiplatform crash reporting system written in C++ by Google"
7arch=(any)
8url="https://github.com/EndstoneMC/sentry-crashpad"
9license=('Apache-2.0')
10makedepends=('python' 'python-pip')
11build() {
12 pip install --no-deps --target="sentry_crashpad" sentry_crashpad==0.7.17.1
13}
14package() {
15 sitepackages=$(python -c "import site; print(site.getsitepackages()[0])")
16 mkdir -p "$pkgdir/$sitepackages"
17 cp -r "$srcdir/sentry_crashpad/*" "$pkgdir/$sitepackages"
18}
19

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