Skip to content

chore(deps): fix two OSV findings and renew the other suppressions - #3606

Merged
markscott-ms merged 1 commit into
finos:mainfrom
rocketstack-matt:gremlin/architecture-as-code-2
Nov 2, 2026
Merged

markscott-ms merged 1 commit into
finos:mainfrom
rocketstack-matt:gremlin/architecture-as-code-2

Conversation

@rocketstack-matt

Copy link
Copy Markdown
Member

Description

Two OSV suppressions now have a real fix. The other 13 have no reachable fix, so this PR keeps them with accurate reasons and new re-review dates. GHSA-ccrj-gw8r-854m expires on 2026-11-30, which would then make main fail the OSV check again.

Advisory Package Result
GHSA-ch52-4w7c-c8xp http-cache-semantics Fixed: 4.3.0 (GitHub also withdrew the advisory)
GHSA-xcx6-jx8p-x3h5 @azure/msal-node Fixed: @azure/identity 4.14.1 brings msal-node 7.1.2
GHSA-238p katex Kept: mermaid 12 moves to katex 0.18, but @mermaid-js/layout-elk 1.0.1 (latest) still bundles katex 0.16.47
GHSA-rxp7, undici x5, GHSA-3g3m ip-address, undici, glob Kept: bundled inside npm. npm 12.2.1 bundles the same versions
GHSA-g3hv minimatch Kept: the latest eslint plugins, spectral-core and serve-handler still use minimatch 3
GHSA-27mw, GHSA-pfhg @sveltejs/kit Kept: fix only in kit 3 (needs TypeScript 6 and Vite 8)
GHSA-gcqx deepmerge Kept: no patched release
GHSA-ccrj opentelemetry-api Kept until 2027-02-28: Quarkus 3.40 LTS still manages 1.62.0

Kept entries now expire on 2027-03-31 (GHSA-ccrj on 2027-02-28). osv-scanner.toml and vex/calm.openvex.json list the same ids. The lockfile changes come from npm update --package-lock-only. There are no manifest changes.

Open PRs that failed OSV before the recent fixes on main (#3577, #3589–#3598) pass after an update from main.

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🎨 Code style/formatting changes
  • ♻️ Refactoring (no functional changes)
  • ⚡ Performance improvements
  • ✅ Test additions or updates
  • 🔧 Chore (maintenance, dependencies, CI, etc.)

Affected Components

  • CLI (cli/)
  • Schema (calm/)
  • CALM AI (calm-ai/)
  • CALM Hub (calm-hub/)
  • CALM Hub UI (calm-hub-ui/)
  • CALM Lab (calm-lab/)
  • CALM Models (calm-models/)
  • CALM Server (calm-server/)
  • CALM Studio (calm-studio/)
  • CALM Widgets (calm-widgets/)
  • CALMGuard (calm-guard/)
  • Documentation (docs/)
  • Shared (shared/)
  • VS Code Extension (calm-plugins/vscode/)
  • Dependencies
  • CI/CD

Commit Message Format ✅

Testing

  • I have tested my changes locally
  • I have added/updated unit tests
  • All existing tests pass

npm run build, npm run lint, the lockfile platform check and vsce package pass. npm test passes, except 5 shared e2e tests that need network access to calm.finos.org, which the sandbox blocks. osv-scanner could not reach api.osv.dev in the sandbox, so the OSV check on this PR is the first full scan.

Checklist

  • My commits follow the conventional commit format
  • I have updated documentation if necessary
  • I have added tests for my changes (if applicable)
  • My changes follow the project's coding standards

Update http-cache-semantics to 4.3.0 and @azure/identity to 4.14.1, which
moves @azure/msal-node to 7.1.2. Remove the suppressions and VEX statements
for GHSA-ch52-4w7c-c8xp and GHSA-xcx6-jx8p-x3h5.

Keep the other 13 suppressions, because no reachable release has the fix.
Update their reasons and move their re-review dates to 2027-03-31
(GHSA-ccrj-gw8r-854m to 2027-02-28).
@rocketstack-matt
rocketstack-matt requested a review from a team as a code owner November 2, 2026 17:34
@github-actions github-actions Bot added the config label Nov 2, 2026
@markscott-ms
markscott-ms merged commit 9d0a8e6 into finos:main Nov 2, 2026
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants