Check the report below, then download or share it. Download PDF Open PDF Back to results

MalDet · Static Security Report

cliamp

github.com/bjarneo/cliamp
Scanned 29 October 2026 at 10:21  ·  Report generated 29 October 2026  ·  Go  ·  4,540 stars
Overall assessment
High
Combined score 86  ·  51 findings after filtering

Summary

32 findings likely need attention, 10 look like noise. Most notable: Missing mutex unlock (`p.mu` variable) before returning from a function. This could re... (99% confidence).

Generated from finding counts. A plain-English summary was not available for this scan.

Risk, by type

MalDet scores two different questions separately, because they call for different responses: code can be badly written without being hostile, and hostile code is not always badly written.

Vulnerability
Medium (80)
Insecure coding an attacker could exploit. Usually mistakes, and usually fixable in place.
Malicious pattern
Low (6)
Signs the code may be trying to do harm: hidden payloads, credential access, persistence, exfiltration.

What each detector found

DetectorLooks for HighMediumLowTotal
semgrep Insecure coding patterns across many languages 5 33 0 38
yara Signatures of malicious behaviour in source files 9 0 1 10
guarddog Malicious package and install-time behaviour 0 1 2 3

32 of 51 findings were rated more likely genuine than noise by the classifier.

Evidence

Identical findings are grouped, so a single rule firing many times takes one row. Ordered worst first. “Seen” is how many times that finding occurred.

SeverityDetectorFindingSeenExample location
high semgrep Missing mutex unlock (`p.mu` variable) before returning from a function. This could result in panics resulting from double lock operations 1 /external/local/provider.go:105
high semgrep Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use 1 /.github/workflows/aur.yml:20
high semgrep Generic Secret detected 1 /external/tidal/creds.go:16
high semgrep Detected non-static command inside Command. Audit the input to 'exec.Command'. If unverified user data can reach this call site, this is a code injection vulnerability. A malicious actor can inject a malicious script to execute arbitrary code. 2 /cmd/protocol.go:116
high yara YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone 9 /site/og-image.svg
medium semgrep This GitHub Actions workflow file uses `workflow_run` and checks out code from the incoming pull request. When using `workflow_run`, the Action runs in the context of the target repository, which includes access to all repository secrets. Normally, this is safe because the Action only runs code from 1 /.github/workflows/aur.yml:13
medium guarddog Detects URLs to suspicious domains often used for exfiltration or C2 [threat-network-exfiltration] 1 /external/radio/channels.go:19
medium semgrep An HTTP redirect was found to be crafted from user-input `r`. This can lead to open redirect vulnerabilities, potentially allowing attackers to redirect users to malicious web sites. It is recommend where possible to not allow user-input to craft the redirect URL. When user-input is necessary to cra 1 /external/spotify/session.go:430
medium semgrep Detected MD5 hash algorithm which is considered insecure. MD5 is not collision resistant and is therefore not suitable as a cryptographic signature. Use SHA256 or SHA3 instead. 4 /luaplugin/api_crypto.go:18
medium semgrep `MinVersion` is missing from this TLS configuration. By default, as of Go 1.22, TLS 1.2 is currently used as the minimum. General purpose web applications should default to TLS 1.3 with all other protocols disabled. Only where it is known that a web server must support legacy clients with unsuppor 1 /internal/httpclient/client.go:236
medium semgrep GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: ac 19 /.github/workflows/release.yml:34
medium semgrep Detected directly writing or similar in 'http.ResponseWriter.write()'. This bypasses HTML escaping that prevents cross-site scripting vulnerabilities. Instead, use the 'html/template' package and render data using 'template.Execute()'. 1 /external/ytmusic/session.go:235
medium semgrep Do not use `math/rand`. Use `crypto/rand` instead. 3 /playlist/playlist.go:6
medium semgrep This tag is missing an 'integrity' subresource integrity attribute. The 'integrity' attribute allows for the browser to verify that externally hosted files (for example from a CDN) are delivered without unexpected manipulation. Without this attribute, if an attacker can modify the externally hosted 3 /site/index.html:618
low guarddog Detects reading of environment variables (credential access, often contains secrets) [threat-runtime-environment-read] 2 /external/lyrion/client.go:121
low yara YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version 1 /site/install.sh

How to read this report