[dependabot]

Bumps homeofe/supply-chain-guard from 6.0.10 to 6.5.9.

Release notes

Sourced from homeofe/supply-chain-guard's releases.

supply-chain-guard v6.5.9

[6.5.9] - 2026-10-18

Added

• Threat intel for 2026-10-18: 22 package entries from the GitHub Advisory Database, OpenSSF and the DataDog dataset (21 in the offline bundle, 1 in the catalog). PyPI: leakdeep (5 versions), ukraine69 (8 versions) and eight single-release TTS/ASR-themed names (voltswannts, tonemaptts, quasitonnts, pyrechoasr, novalithtts, glassbeakasr, driftwavets, emberlytts). npm: coderabbit@0.0.0-dev-202603280606, the unpublished dev version DataDog holds a sample of (catalog); coderabbit 0.9.0 stays unblocked.
• Threat intel for 2026-10-17: 33 package entries from the GitHub Advisory Database and OpenSSF, all in the offline bundle. Clusters: seven @beloved-lenora/opencode-* plugin packages, parxleys and @xatancchii/natabaileys (all now npm security holding packages); dependency-confusion pins in @flexmr/ (13), @newspage/ (5) and @accenturecodefoundry/ (1); itsa-react-maskedinput@16.1.2 and itsa-react-focuscontainer@16.0.10; PyPI marocolor@1.0.0 and pyyi 2.4 / 2.4.2.

Changed

• The bundle cutoff advances from 2026-09-16 to 2026-09-18, and 61 plain package entries dated 2026-09-16 move from the offline bundle to the catalog. None carries a campaign or family, and no test or document names any of them.
• Node support policy: the nodejs/Release schedule, re-read on 2026-10-18, is unchanged (Node 24 Active LTS until 2026-10-20, Node 26 from 2026-10-28), so activeLtsMajor stays 24 and the review milestone moves to 6.5.10.

Removed

• 58 bare npm names from the DataDog dataset (57 in the bundle, 1 in the catalog) that blocked names reserved by their owners or by researchers, not taken down by npm: their only versions are -security releases published by the name's own account ("Reserved for Paysafe Group", "Reserved for security reasons", a researcher's hold on @tekionai/mcp-client, and mcp-secure-server, a live package whose author names every release -security). A name block flagged the owner of the name. The dataset holds no malware sample for any of them, and the corrected importer proposes nothing for them. Listed in .ai/handoff/STATUS.md.
• Eight more DataDog name blocks, each reviewed by hand: the Windows binary packages agentlocks-win32-x64, foremerge-win32-x64 and raster-bin-win32-x64 of three open-source projects (npm placed its holding release within seconds of the first upload, then the authors published again), coderabbit (CodeRabbit's own npm installer; the dataset's sample is only the deleted 0.0.0-dev-202603280606, which the importer pins), and four takedown test packages of kartykgithub. @itsmee_aizat.id/baileys2

... (truncated)

Changelog

Sourced from homeofe/supply-chain-guard's changelog.

[6.5.9] - 2026-10-18

Added

• Threat intel for 2026-10-18: 22 package entries from the GitHub Advisory Database, OpenSSF and the DataDog dataset (21 in the offline bundle, 1 in the catalog). PyPI: leakdeep (5 versions), ukraine69 (8 versions) and eight single-release TTS/ASR-themed names (voltswannts, tonemaptts, quasitonnts, pyrechoasr, novalithtts, glassbeakasr, driftwavets, emberlytts). npm: coderabbit@0.0.0-dev-202603280606, the unpublished dev version DataDog holds a sample of (catalog); coderabbit 0.9.0 stays unblocked.
• Threat intel for 2026-10-17: 33 package entries from the GitHub Advisory Database and OpenSSF, all in the offline bundle. Clusters: seven @beloved-lenora/opencode-* plugin packages, parxleys and @xatancchii/natabaileys (all now npm security holding packages); dependency-confusion pins in @flexmr/ (13), @newspage/ (5) and @accenturecodefoundry/ (1); itsa-react-maskedinput@16.1.2 and itsa-react-focuscontainer@16.0.10; PyPI marocolor@1.0.0 and pyyi 2.4 / 2.4.2.

Changed

• The bundle cutoff advances from 2026-09-16 to 2026-09-18, and 61 plain package entries dated 2026-09-16 move from the offline bundle to the catalog. None carries a campaign or family, and no test or document names any of them.
• Node support policy: the nodejs/Release schedule, re-read on 2026-10-18, is unchanged (Node 24 Active LTS until 2026-10-20, Node 26 from 2026-10-28), so activeLtsMajor stays 24 and the review milestone moves to 6.5.10.

Removed

• 58 bare npm names from the DataDog dataset (57 in the bundle, 1 in the catalog) that blocked names reserved by their owners or by researchers, not taken down by npm: their only versions are -security releases published by the name's own account ("Reserved for Paysafe Group", "Reserved for security reasons", a researcher's hold on @tekionai/mcp-client, and mcp-secure-server, a live package whose author names every release -security). A name block flagged the owner of the name. The dataset holds no malware sample for any of them, and the corrected importer proposes nothing for them. Listed in .ai/handoff/STATUS.md.
• Eight more DataDog name blocks, each reviewed by hand: the Windows binary packages agentlocks-win32-x64, foremerge-win32-x64 and raster-bin-win32-x64 of three open-source projects (npm placed its holding release within seconds of the first upload, then the authors published again), coderabbit (CodeRabbit's own npm installer; the dataset's sample is only the deleted 0.0.0-dev-202603280606, which the importer pins), and four takedown test packages of kartykgithub. @itsmee_aizat.id/baileys2 stays blocked: every release is the malware actor's and npm holds the name.

... (truncated)

Commits

• 26ee014 chore(release): prepare v6.5.9 (#423)
• 8d6271e feat(threat-intel): IOCs for 2026-10-18 (#422)
• 86414e2 fix(threat-intel): remove eight reviewed DataDog name blocks (#421)
• d154fbf fix(threat-intel): remove 58 DataDog name blocks on reserved names (#420)
• 7de87e3 feat(threat-intel): IOCs for 2026-10-17 (#417)
• f5f8fd4 fix(feed-import): a name live again after an npm takedown is not a removed pa...
• b15c77a fix(publish): pin npm 11.21.1, clearing the twelve advisories in npm's bundle...
• 078c2dc chore(release): prepare v6.5.8 (#416)
• 9eb2c0a feat(threat-intel): pin composer slimfit/formbase 1.3 (#415)
• c1ac167 chore(deps): bump the github-actions group with 6 updates (#413)
• Additional commits viewable 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)

[github-actions]

supply-chain-guard Scan Report

WARNING: Findings were detected.

Canonical JSON report: 3 reportable finding(s).

## 🛡️ supply-chain-guard Scan Report

| Property | Value |
|----------|-------|
| Tool | `supply-chain-guard v6.5.9` |
| Target | `.` |
| Type | directory |
| Time | 2026-10-21T22:54:09.584Z |
| Commit | `045cfcc523eff0599253b2de0c9a25cd60a5df68` |
| Detection Set | `v6.5.9 (7052 entries, generated 2026-10-18T00:00:00.000Z)` |
| **Catalog** | **Bundled indicators only: 264,096 historical catalog indicators were not consulted, because the catalog has not been downloaded. Run "supply-chain-guard feed refresh" (in the GitHub Action, set refresh-catalog: true) to include them.** |
| Duration | 1567ms |
| **Risk Score** | **9/100** (LOW) |

### Summary

Scanned 83 of 88 files.

🟡 1 medium | 🔵 2 low

### Findings

#### 🟡 [MEDIUM] Workflow grants the OIDC id-token: write permission. Any step in a job that holds it can request a token for the workflow's cloud identity. This check reports the permission itself and does not inspect which steps run with it.

- **Rule:** `GHA_OIDC_WRITE_PERM`
- **File:** `.github/workflows/release.yml:388`
- **Match:** `id-token: write`
- **Recommendation:** Grant id-token: write only on the job that needs it, and review that job's actions and run steps: any of them can request the OIDC token.

#### 🔵 [LOW] Action "homeofe/supply-chain-guard@v6.5.9" uses a version tag instead of a commit SHA. Tags can be force-pushed to point to different commits.

- **Rule:** `GHA_TAG_NOT_SHA`
- **File:** `.github/workflows/supply-chain-guard.yml:25`
- **Match:** `homeofe/supply-chain-guard@v6.5.9`
- **Recommendation:** Consider pinning this action to a full commit SHA for maximum security. Tags can be moved to point to malicious code.

#### 🔵 [LOW] Action "homeofe/supply-chain-guard@v6.5.9" is from third-party owner "homeofe". Third-party actions can be compromised.

- **Rule:** `GHA_THIRD_PARTY_ACTION`
- **File:** `.github/workflows/supply-chain-guard.yml:25`
- **Match:** `homeofe/supply-chain-guard@v6.5.9`
- **Recommendation:** Pin "homeofe/supply-chain-guard@v6.5.9" to a specific commit SHA and audit the action source code before use.

### Recommendations

- Review the listed findings and assess whether they represent legitimate functionality or potential threats.

---
*Generated by [supply-chain-guard](https://github.com/homeofe/supply-chain-guard)*