fix(deps): remediate HIGH Dependabot alerts via lockfile updates - #84
Merged
Conversation
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
unwakuche-ld
approved these changes
Aug 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issues
Open Dependabot alerts on
launchdarkly/mcp-server(60 open, all againstpackage-lock.json; no CRITICAL, 13 distinct HIGH).Describe the solution you've provided
package-lock.jsononly — nopackage.jsonconstraint changes were needed; every fix was reachable inside the existing semver ranges vianpm audit fix(no lockfile hand-editing, no overrides/resolutions).Key bumps (all transitive):
hono/@hono/node-server@modelcontextprotocol/sdkfast-uriajvexpress-rate-limit/ip-address@modelcontextprotocol/sdkpath-to-regexpexpress4 /routerjs-yamleslintflattedeslintglob/minimatch/brace-expansiontshy,eslint,typescript-eslintpicomatchchokidar,micromatchqs/body-parserexpressRemediated HIGH GHSAs: GHSA-5j98-mcp5-4vw2 (glob), GHSA-7r86-cg39-jmmj (minimatch), GHSA-wc8c-qw6v-h7f6 (@hono/node-server), GHSA-q5qw-h33p-qvwr + GHSA-88fw-hqm2-52qc (hono), GHSA-46wh-pxpv-q5gq (express-rate-limit), GHSA-rf6f-7fwh-wjgh (flatted), GHSA-j3q9-mxjg-w52f + GHSA-37ch-88jc-xwx2 (path-to-regexp), GHSA-4c8g-83qw-93j6 / GHSA-v2hh-gcrm-f6hx / GHSA-7p8r-x3mc-p8w7 / GHSA-q3j6-qgpj-74h6 / GHSA-v39h-62p7-jpjc (fast-uri), GHSA-52cp-r559-cp3m + GHSA-5p4m-2wfm-xmqj (js-yaml), GHSA-3jxr-9vmj-r5cp (brace-expansion), GHSA-mwp4-54f8-5fhr (ip-address).
The MODERATE/LOW alerts (hono advisory chain up to 4.12.34, qs, picomatch, body-parser, ip-address, js-yaml 4.2.0) came along for free with the same upgrades.
npm auditnow reports 0 vulnerabilities.No HIGH/CRITICAL alert was left unremediated.
Describe alternatives you've considered
Bumping
@modelcontextprotocol/sdkto 1.30.0 orexpress(dev dep) to 5.x — unnecessary, since the vulnerable transitives resolve to patched versions with the current direct dependency ranges. Kept the diff to the lockfile to minimize risk.Additional context
Verified locally:
npm installclean,npm run lintclean,npm run build(bun build + tshy) succeeds. The repo has no test script.Link to Devin session: https://app.devin.ai/sessions/a4e331be04834dc2a6e7bee92c8bb8f5
Requested by: @pkaeding