build(deps): Bump actions/dependency-review-action from 4 to 4.9.0

[dependabot]

Bumps actions/dependency-review-action from 4 to 4.9.0.

Release notes

Sourced from actions/dependency-review-action's releases.

Dependency Review Action 4.9.0

This feature release contains a couple of notable changes:

• There is a new configuration option show_patched_versions which will add a column to the output, showing the fix version of each vulnerable dependency. Thanks @​felickz!
• Runs which do not display OpenSSF scorecards no longer fetch scorecard information; previously it was fetched regardless of whether or not it was displayed, causing unneccessary slowness. Great catch @​jantiebot!
• There are a couple of fixes to purl parsing which should improve match accuracy for allow-package-dependency lists, including case (in)sensitivity and url-encoded namespaces Thanks @​juxtin!

What's Changed

• Compare normalized purls to account for encoding quirks by @​juxtin in actions/dependency-review-action#1056
• Make purl comparisons case insensitive by @​juxtin in actions/dependency-review-action#1057
• Feat: Add Patched Version to Vulnerabilities summary by @​felickz in actions/dependency-review-action#1045
• fix: only get scorecard levels if user wants to see the OpenSSF scorecard by @​jantiebot in actions/dependency-review-action#1060
• Bump actions/stale from 10.1.0 to 10.2.0 by @​dependabot[bot] in actions/dependency-review-action#1058
• Bump actions/checkout from 4 to 6 by @​dependabot[bot] in actions/dependency-review-action#1021
• Updates for release 4.9.0 by @​ahpook in actions/dependency-review-action#1064

New Contributors

• @​jantiebot made their first contribution in actions/dependency-review-action#1060

Full Changelog: actions/dependency-review-action@v4.8.3...v4.9.0

4.8.3

Dependency Review Action v4.8.3

This is a bugfix release that updates a number of upstream dependencies and includes a fix for the earlier feature that detected oversized summaries and upload them as artifacts, which could occasionally crash the action.

We have also updated the release process to use a long-lived v4 branch for the action, instead of a force-pushed tag, which aligns better with git branching strategies; the change should be transparent to end users.

What's Changed

• GitHub Actions can't push to our protected main by @​dangoor in actions/dependency-review-action#1017
• Bump actions/stale from 9.1.0 to 10.1.0 by @​dependabot[bot] in actions/dependency-review-action#995
• Bump github/codeql-action from 3 to 4 by @​dependabot[bot] in actions/dependency-review-action#1003
• Bump actions/setup-node from 4 to 6 by @​dependabot[bot] in actions/dependency-review-action#1005
• Upgrade glob to address a vulnerability by @​brrygrdn in actions/dependency-review-action#1024
• Bump js-yaml by @​dependabot[bot] in actions/dependency-review-action#1020
• Addressing vulnerabilities by @​Ahmed3lmallah in actions/dependency-review-action#1036
• Bump fast-xml-parser from 5.3.3 to 5.3.5 by @​dependabot[bot] in actions/dependency-review-action#1050
• Bump fast-xml-parser from 5.3.5 to 5.3.6 by @​dependabot[bot] in actions/dependency-review-action#1053
• Properly truncate long summaries and catch errors by @​juxtin in actions/dependency-review-action#1052
• Bump spdx-expression-parse from 3.0.1 to 4.0.0 in the spdx-licenses group across 1 directory by @​dependabot[bot] in actions/dependency-review-action#931
• Changes for Release 4.8.3 by @​ahpook in actions/dependency-review-action#1054

Full Changelog: https://github.com/actions/dependency-review-action/compare/v4.8.2..v4.8.3

v4.8.2

Minor fixes:

• Fix PURL parsing for scoped packages (#1008 from @​danielhardej)
• Fix for large summaries (#1007 from @​gitulisca)

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Note

Low Risk
Low risk GitHub Actions workflow change that only updates the pinned version of actions/dependency-review-action; behavior changes are limited to dependency-review reporting/performance in CI.

Overview
Updates the .github/workflows/dependency-review.yml workflow to pin actions/dependency-review-action from v4 to v4.9.0.

No other workflow logic or policy inputs (license allow/deny lists) are changed.

^{Reviewed by Cursor Bugbot for commit cb79280. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

🤖 Cursor Dependency Analysis

Supply-Chain Malware Review

Checking how the action is referenced in the repository for context.

Verdict: benign

Why this looks safe

• Publisher: actions/dependency-review-action lives under GitHub’s official actions org—the same line as other first-party Actions. That is strong supply-chain context for this bump.
• Scanner vs. interpretation: The report is warn only, with no Unicode, confusable, or IOC hits. The two heuristic hits (version_jump_anomaly and maintainer_drift for 4 → 4.9.0) match Dependabot pinning a moving v4 ref to an exact patch release, not evidence of compromise; the npm-maintainers-style heuristic is a poor fit for a GitHub Action published by GitHub.
• Repo usage: Your workflow only checks out the repo and runs dependency review with license knobs—no unusual steps, secrets, or extra network surface beyond what the action is meant to do (see .github/workflows/dependency-review.yml).
• Upstream narrative: Release notes describe additive options, performance (skip scorecard fetch when unused), and PURL matching fixes—consistent with a normal minor/feature release, not a trojan pattern.

Action: Safe to merge from a malware/supply-chain standpoint; rely on CI green + your usual review. The heuristic warnings can be treated as noise unless your policy requires human sign-off on all scanner warns regardless of cause.

Compatibility Analysis

Searching the repo for dependency-review-action usage and checking workflow configuration against upstream changes.

1) Where it’s used

Only one call site in real workflow YAML:

•     - name: "Dependency Review"
        uses: actions/dependency-review-action@v4.9.0
        with:
          allow-dependencies-licenses: pkg:npm/node-forge
          deny-licenses: AGPL-1.0-only, AGPL-1.0-or-later, AGPL-1.0-or-later, AGPL-3.0-or-later, GPL-1.0-only, GPL-1.0-or-later, GPL-2.0-only, GPL-2.0-or-later, GPL-3.0-only, GPL-3.0-or-later

`dependency-cursor-review.yml` only names a job `dependency-review`; it does **not** use this action. Other `rg` hits under `malware_scan_*`, JSON, etc. are tooling artifacts, not usage.

---

## 2) Overlap with 4.9.0 / recent upstream behavior

| Your usage | Relevant release / upstream change? |
|------------|--------------------------------------|
| `allow-dependencies-licenses` (`pkg:npm/node-forge`) | **Yes, indirectly.** Notes and PRs describe **PURL normalization** (encoding, case) for allow/deny-style lists. That can change whether an allowlist entry matches; here it’s more likely to **fix** mis-matches than to break a correct `pkg:` string. |
| `deny-licenses` | **No API removal** in `action.yml`; license inputs unchanged. |
| `show-patched-versions`, scorecard fetching | **Not configured.** New column is opt-in; scorecard change is internal (skip fetch when not shown). |

Upstream `action.yml` in `.upstream-dependency` still documents `allow-dependencies-licenses`, `deny-licenses`, etc., and adds `show-patched-versions` (optional). The action’s `runs.using` is **`node24`** — that affects the **action’s** runtime on GitHub’s runners, not your repo’s build.

---

## 3) Risks / unknowns

- **Self-hosted / non-standard runners:** If anything other than GitHub-hosted `ubuntu-latest` (or equivalent) ran this, you’d want to confirm JS actions on **Node 24** are supported there. For `runs-on: ubuntu-latest` on github.com, this is normally fine.
- **Allowlist matching:** Slightly more plausible behavior change for `pkg:npm/node-forge` if manifests ever used odd casing/encoding; low probability for a standard npm package PURL.

---

## 4) Recommendation

**Merge** — same major line (`v4` → `v4.9.0`), existing inputs still supported, changes are additive or correctness/performance-related with no required workflow edits. Optional: enable `show-patched-versions: true` later if you want the extra column in logs/PR summaries; not required for the bump.

---

## Malware Scan Summary

- Status: **warn**
- Warn only mode: `true`
- Changed upstream files scanned: `0`
- Resolution strategy: `to_version_single_commit`
- Changed node/vendor paths: `0`
- Changed lockfiles: `0`
- Resolved refs: from=`n/a` to=`2031cfc080254a8a887f58cffee85186f0e49e48`
- Unicode findings (post-allowlist): `0`
- Confusable findings (post-allowlist): `0`
- IOC findings (post-allowlist): `0`
- Heuristic findings (post-allowlist): `2`

### Top findings
- `actions/dependency-review-action:0` version_jump_anomaly :: `4->4.9.0`
- `actions/dependency-review-action:0` maintainer_drift :: `4->4.9.0`