cli-forge-publish

Warn

Audited by Snyk on Apr 21, 2026

Risk Level: MEDIUM
Full Analysis

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (high risk: 0.90). The release workflow explicitly downloads and inspects public, user-controlled content from GitHub Releases and the npm registry (for example, templates/dot-github/workflows/release.yml uses gh release view / actions/download-artifact / curl to GitHub and runs npm view, and the node scripts read dist/provenance.json and npm metadata), so untrusted third‑party content is read and used to decide publish/recover actions.

MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).

  • Potentially malicious external URL detected (high risk: 0.80). The GitHub Actions workflow fetches and executes remote build tooling at runtime—for example the workflow's setup step downloads the llvm-mingw archive via curl ("https://github.com/mstorsjo/llvm-mingw/releases/download/${llvm_mingw_version}/${archive}") which is required for the build and results in executing remote-provided binaries—so this is a runtime external dependency that executes remote code.

Issues (2)

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

W012
MEDIUM

Unverifiable external dependency detected (runtime URL that controls agent).

Audit Metadata
Risk Level
MEDIUM
Analyzed
Apr 21, 2026, 08:47 AM
Issues
2
Security Audit — snyk — cli-forge-publish