Security context

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

rollup/rollup
master @ ff0a94b
3
Fixes
2
CVEs
CRITICAL
Peak severity
Highlights
Code Injection: 1 prior fix. Scrutinize any change in this area.
.github/workflows: most-fixed (1 issue). Treat as high-risk during review.
3 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

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

Path Traversal: Insecure file name sanitization in the bundling engine allows attackers controlling output filenames to escape the designated output directory and write arbitrary files, potentially leading to remote code execution. This is a highly critical threat that historically impacted several major versions.
Credential Leak: Using a highly-privileged workflow trigger like pull_request_target alongside untrusted code checkouts exposes repository secrets and credentials to untrusted PR authors.
Code Injection: Checking out mutable pull request references (such as the merge ref) rather than pinning the checkout to a immutable head SHA introduces race conditions where malicious code can be injected and executed in privileged runner environments.