Repository navigation
chore(deps): resolve open Dependabot security alerts - #43
Merged
Merged
Conversation
Refreshes vulnerable transitive dependencies to patched releases within their parents' existing semver ranges: - proxy-addr 2.0.7 -> 2.0.8 (express) - hono 4.13.1 -> 4.13.13 (@modelcontextprotocol/sdk) - ip-address 10.5.0 -> 10.7.4 (express-rate-limit) - undici 6.28.0 -> 6.29.1 (node-gyp) - fast-uri 3.1.5 -> 3.1.9 (ajv) - browserslist 4.28.1 -> 4.29.4, baseline-browser-mapping 2.9.11 -> 2.11.30 (@babel/helper-compilation-targets) sprintf-js has no patched release. Its only path was @istanbuljs/load-nyc-config -> js-yaml@3 -> argparse@1, and js-yaml@3 only needs argparse for its CLI. A resolution points load-nyc-config at the js-yaml ^5.4.2 already in the tree (it only calls js-yaml.load), which drops js-yaml@3, argparse@1, esprima and sprintf-js and clears the js-yaml 3.x alert too. The dist manifest no longer carries the root-only resolutions field.
|
Add Carrot credits or activate Agent usage billing to use Autofix |
Contributor
Author
|
@coderabbitai review |
✅ Action performedReview finished.
|
Contributor
Cherry-pick CreatedA cherry-pick PR to Please review and merge if this change should also be in If the cherry-pick is not needed, close the PR. |
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.
Summary
Resolves all 19 open Dependabot alerts. Every affected package is a transitive dev-tree dependency. The published package's runtime dependencies (
@apidevtools/json-schema-ref-parser,openapi-types,yaml) are unchanged.Lockfile refresh within existing ranges
Each patched version satisfies its parent's existing semver range, so only
yarn.lockchanges for these:proxy-addrexpress(MCP SDK)fast-uriajvundicinode-gyp(via@parcel/watcher, jest)browserslist@babel/helper-compilation-targetsbaseline-browser-mappingbrowserslisthono@modelcontextprotocol/sdktoSSGpath escape, query-after-fragmentip-addressexpress-rate-limitfe80::/10, NAT64 local-usebrowserslist's own data packages (caniuse-lite,electron-to-chromium,node-releases,update-browserslist-db) move with it.sprintf-js(no patched release) andjs-yaml3.xsprintf-js≤ 1.1.3 is affected, and 1.1.3 is the latest release. Its only path in the tree wasbabel-plugin-istanbul → @istanbuljs/load-nyc-config → js-yaml@3 → argparse@1 → sprintf-js.js-yaml@3needsargparseonly for its CLI, andload-nyc-configonly callsrequire('js-yaml').load(...), and only for a.nycrc.yaml(this repo has none). Aresolutionsentry points@istanbuljs/load-nyc-config/js-yamlat the^5.4.2already in the tree forjson-schema-ref-parser. js-yaml 5 ships a CommonJS build withload. That removesjs-yaml@3,argparse@1,esprimaandsprintf-js, which also clears the js-yaml 3.x merge-key alert.Build
scripts/strip-dist-from-pkg.jsnow deletesresolutionsfrom the publisheddist/package.json(next toscripts). The field only means something in the repo root.Verification
yarn install --immutableyarn build, thendist/package.jsonanddist/esm/package.jsonchecked for noresolutionstsc --noEmityarn test:coverage: 1102 tests, 100% statements/branches/functions/linesyarn test:e2e: 56 tests. This runs the real MCP SDK, so it exercisesexpress(proxy-addr),express-rate-limit(ip-address),honoandajv(fast-uri), plus the dist packaging story.yarn whyshows every alerted package at or above its first patched version, andsprintf-js/argparse@1/js-yaml@3absent.Summary by CodeRabbit
Bug Fixes
Chores