github-actions

No clear malware or data theft is present. The workflow has a significant shell-injection risk because tag names and manual version input are interpolated into shell source before validation. The changelog's fixed GITHUB_OUTPUT delimiter also creates a potential output-injection issue from crafted commit messages. Review and harden these input-handling paths before use.

The action has a shell-injection and step-output-injection risk because the caller-controlled working-directory input is interpolated directly into a run script and written to GITHUB_OUTPUT without safe encoding. Corepack's use of repository metadata or `latest` also makes package-manager version selection less reproducible. No direct malware behavior is evident in this fragment.

The action has security risks in handling configurable Git refs and arbitrary filenames: direct expression interpolation into shell source can enable command injection, and the fixed output delimiter can permit GitHub Actions output injection. Mapping regex behavior and unescaped fallback JSON also merit correction. The fragment does not show clear malicious intent or malware.