Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

realm/swiftlint

              main @ 962e0f8
            

Fixes

CVEs

HIGH

Peak severity

Highlights

Command Injection: 1 prior fix. Scrutinize any change in this area.

GitHub: most-fixed (2 issues). Treat as high-risk during review.

1 high-severity fix in this history; regressions here are high-impact.

Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Command Injection: Using direct GitHub Actions expression interpolation inside shell run scripts allows attackers to execute arbitrary code on the runner by manipulating pull request titles, branch names, or other issue inputs. Developers should always pass these variables via secure environment variables.

Credential Exposure: By default, the actions/checkout step persists GitHub credentials on disk within the local .git directory, which can be harvested by subsequent steps or untrusted PR code. Disabling persistence is critical for untrusted runner steps.

Remote Code Execution: Untrusted workspace configurations can override executable paths (such as swiftlint.path), leading to arbitrary command execution when the workspace is opened by an unsuspecting user.