xinghuo-note-bin
This PKGBUILD installs a prebuilt binary extracted from a .deb file downloaded from gitee.com (a Chinese code hosting platform), which is the upstream project's own release page (gitee.com/xinghuowangluo/note/releases). The binary is not built from source and is executed directly. While gitee.com is a legitimate hosting platform (similar to GitHub) and the URL points to the project's own release artifacts with a pinned sha256sum, the supply-chain risk is real: the binary is a closed prebuilt executable from a personal/small project on a third-party platform with no independent verification mechanism beyond the checksum. The sha256sum provides integrity but not authenticity — if the release was replaced at the same tag, the checksum would catch it, but the maintainer must keep it updated. This is a standard -bin AUR pattern but with a non-Western hosting platform and an unauditable binary, which warrants medium severity rather than clean.
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:17
"LICENSE-${pkgver}::https://gitee.com/xinghuowangluo/note/blob/v${pkgver}/LICENSE"
llm_review
An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): This PKGBUILD installs a prebuilt binary extracted from a .deb file downloaded from gitee.com (a Chinese code hosting platform), which is the upstream project's own release page (gitee.com/xinghuowangluo/note/releases). The binary is not built from source and is executed directly. While gitee.com is a legitimate hosting platform (similar to GitHub) and the URL points to the project's own release artifacts with a pinned sha256sum, the supply-chain risk is real: the binary is a closed prebuilt executable from a personal/small project on a third-party platform with no independent verification mechanism beyond the checksum. The sha256sum provides integrity but not authenticity — if the release was replaced at the same tag, the checksum would catch it, but the maintainer must keep it updated. This is a standard -bin AUR pattern but with a non-Western hosting platform and an unauditable binary, which warrants medium severity rather than clean.
PKGBUILD
1 offending line(s) highlighted# Maintainer: zxp19821005 <zxp19821005 at 163 dot com>
pkgname=xinghuo-note-bin
_debname=com.gitee.xinghuo.note
pkgver=1.6.4
pkgrel=1
pkgdesc="Note Master, a convenient note-taking tool for recording temporary information, reminders, or to-do tasks on the desktop. Beautiful interface, small size, and fast speed.(Prebuilt version)"
arch=('x86_64')
url="https://gitee.com/xinghuowangluo/note"
license=('MulanPSL-2.0')
provides=("${pkgname%-bin}=${pkgver}")
conflicts=("${pkgname%-bin}")
depends=(
'qt6-base'
)
source=(
"${pkgname%-bin}-${pkgver}.deb::${url}/releases/download/v${pkgver}/${_debname}_${pkgver}-20241130_amd64_Deepin23.deb"
"LICENSE-${pkgver}::https://gitee.com/xinghuowangluo/note/blob/v${pkgver}/LICENSE"
)
sha256sums=('4755a3a36973a35fef5fe9450a622c7dd29b71218ed1aa8cf8b346b84a5ef319'
'8a9cc05fde1a7b1ea22e75ac44679619609d332cb1377dc73aaa57f68bdcc80d')
prepare() {
bsdtar -xf "${srcdir}/data."*
sed -i -e "
s/Name=note/Name=Xinghuo Note/g
s/\/opt\/apps\/${_debname}\/bin\/note/${pkgname%-bin}/g
s/\/opt\/apps\/${_debname}\/icon\/note.png/${pkgname%-bin}/g
s/Categories=Application/Categories=Utility;/g
" "${srcdir}/usr/share/applications/note.desktop"
}
package() {
install -Dm755 "${srcdir}/opt/apps/${_debname}/bin/note" "${pkgdir}/usr/bin/${pkgname%-bin}"
install -Dm644 "${srcdir}/opt/apps/${_debname}/icon/note.png" "${pkgdir}/usr/share/pixmaps/${pkgname%-bin}.png"
install -Dm644 "${srcdir}/usr/share/applications/note.desktop" "${pkgdir}/usr/share/applications/${pkgname%-bin}.desktop"
install -Dm644 "${srcdir}/LICENSE-${pkgver}" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
}
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 |