origami-waves
A prebuilt JAR is downloaded from repository.hellonico.info, which is a personal/project-specific Maven repository operated by the same author (hellonico) as the GitHub project (github.com/hellonico/ocean-waves). While the host appears to be the author's own Maven repository rather than a completely unrelated third party, it is still not an official, audited distribution channel (e.g., Maven Central, GitHub Releases). The JAR is executed directly via 'java -jar', meaning any malicious or compromised content would result in code execution. A sha256sum is provided, which mitigates substitution risk somewhat, but the hash only protects against post-download tampering if the source itself was clean at time of hash generation. The core concern is that a personal Maven repository host could be compromised, taken over, or the JAR could have been built from unreviewed sources. This is a genuine, if moderate, supply-chain concern: executed binary from a non-standard personal host with no reproducible build path provided to users.
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:13
source=("https://repository.hellonico.info/repository/hellonico/origami/wave/${pkgver}/wave-${pkgver}.jar")
llm_review
An AI model (anthropic/claude-4.6-sonnet-20260217) reviewed this and agrees it is MEDIUM (confidence 72%): A prebuilt JAR is downloaded from repository.hellonico.info, which is a personal/project-specific Maven repository operated by the same author (hellonico) as the GitHub project (github.com/hellonico/ocean-waves). While the host appears to be the author's own Maven repository rather than a completely unrelated third party, it is still not an official, audited distribution channel (e.g., Maven Central, GitHub Releases). The JAR is executed directly via 'java -jar', meaning any malicious or compromised content would result in code execution. A sha256sum is provided, which mitigates substitution risk somewhat, but the hash only protects against post-download tampering if the source itself was clean at time of hash generation. The core concern is that a personal Maven repository host could be compromised, taken over, or the JAR could have been built from unreviewed sources. This is a genuine, if moderate, supply-chain concern: executed binary from a non-standard personal host with no reproducible build path provided to users.
PKGBUILD
1 offending line(s) highlighted# Maintainer: Your Name <your.email@example.com>
pkgname=origami-waves
pkgver=1.19
pkgrel=1
pkgdesc="Origami Waves: translate your pptx using ollama"
#arch=('x86_64')
arch=('any')
url="https://github.com/hellonico/ocean-waves"
license=('MIT')
depends=('jdk-openjdk>=21')
#makedepends=('clojure' 'deps-edn')
#source=("https://github.com/yourusername/my-clojure-project/releases/download/v${pkgver}/my-clojure-project-${pkgver}.jar")
source=("https://repository.hellonico.info/repository/hellonico/origami/wave/${pkgver}/wave-${pkgver}.jar")
sha256sums=('2d560220d599888594647c5a8cc49499a596e6be6612fde89bdef72e880606da')
build() {
echo "No additional build step required. Uberjar provided."
}
package() {
# Install the jar
install -Dm644 "${srcdir}/wave-${pkgver}.jar" "${pkgdir}/usr/share/${pkgname}/${pkgname}.jar"
# Create a script to run the jar
install -Dm755 /dev/stdin "${pkgdir}/usr/bin/${pkgname}" << EOF
#!/bin/bash
exec java -jar /usr/share/${pkgname}/${pkgname}.jar "\$@"
EOF
# Optional: Install documentation
# install -Dm644 "${srcdir}/README.md" "${pkgdir}/usr/share/doc/${pkgname}/README.md"
}
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 |