Repository navigation
chore(deps): patch website Dependabot advisories - #1187
Merged
Merged
Conversation
Bump brace-expansion, fast-uri, js-yaml (3.x and 4.x lines), and nanoid to their patched versions via package.json overrides / lockfile resolution. All four are transitive under @docusaurus/* or docusaurus-plugin-llms, pulled in by parents whose declared semver ranges already permit the fix (fast-uri, nanoid) or that mix two incompatible major lines (js-yaml 3.x under gray-matter vs 4.x elsewhere), which now get separate nested overrides. image-size (ICNS/JXL/HEIF infinite-loop advisories) has no patched release upstream (2.0.2 is latest). It is only invoked by Docusaurus's markdown image-size transform against files already committed to this repo's docs/static trees at build time -- never attacker- or user-supplied input, and no ICNS/JXL/HEIF file exists in the repo. Risk accepted; left unpatched pending an upstream fix. Verified with a clean `npm ci` + `npm run build` from website/.
Deploying mcpproxy-docs with
|
| Latest commit: |
2a58d05
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://60efadc8.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://deps-website-advisories.mcpproxy-docs.pages.dev |
Dumbris
enabled auto-merge (squash)
September 2, 2026 13:00
Two high-severity browserslist alerts (fix >= 4.28.7) landed against website/package-lock.json while the rest of this branch was in review, so no PR covered them. No override needed: every parent already declares a ^4.x range that admits 4.28.7+, so npm update re-resolved in range. The lockfile diff is browserslist plus its own data-table dependencies (caniuse-lite, electron-to-chromium, node-releases, update-browserslist-db, baseline-browser-mapping) and nothing else. Verified: the lockfile integrity matches the npm registry's published hash for 4.28.8, a clean rm -rf node_modules && npm ci installs from it, and npm run build succeeds (174 documents processed).
Contributor
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 33632120579 --repo smart-mcp-proxy/mcpproxy-go
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
Closes the seven open Dependabot alerts against
website/package-lock.json(the Docusaurus source for docs.mcpproxy.app, built by Cloudflare Pages). All seven are transitive under@docusaurus/*ordocusaurus-plugin-llms; there are no directwebsite/package.jsondependencies among them.5.0.8 -> 5.0.9via the existingoverrides["brace-expansion"]entry (repo already forces one version acrossminimatch@3andminimatch@9; bumped the pin).3.1.4 -> 3.1.7(>=3.1.5 required). Its only parent,ajv@8.20.0(underwebpack-dev-server), already declares^3.0.1, sonpm update fast-urire-resolved within the existing range — no override needed, nopackage.jsonchange beyond the diff below.!!omapresolution (GHSA-5p4m-2wfm-xmqj)3.15.0 -> 3.15.2(>=3.15.1 required) undergray-matter@4.0.3(pulled in bydocusaurus-plugin-llms), via a nestedoverrides["gray-matter"]["js-yaml"]entry so only that branch is touched.4.3.0 -> 4.3.2(>=4.3.1 required) everywhere else in the tree (@docusaurus/utils-validation,cosmiconfig,@11ty/gray-matter,@docusaurus/plugin-content-docs, all of which declare^4.1.0), via a top-leveloverrides["js-yaml"]entry. Kept separate from the 3.x line above because a single blanket override would have forcedgray-matter's 3.x-API consumer onto the incompatible 4.x major.sizeis 0 (GHSA-2v37-7h3g-55p8)3.3.16 -> 3.3.18. Its only parent,postcss@8.5.24(under@docusaurus/bundler), declares^3.3.16, sonpm update nanoidre-resolved within range — no override, nopackage.jsonchange.2.0.2is the latest published release; the advisory range is<=2.0.2. See reachability assessment below.image-size reachability assessment
image-sizeis pulled in solely by@docusaurus/mdx-loader, which callsimageSizeFromFile()from exactly one place:remark/transformImage/index.js, Docusaurus's remark plugin that auto-injectswidth/heightonto<img>tags rendered from local Markdown images.Tracing that call site:
getLocalImageAbsolutePath()— i.e. files already present in this repo'sdocs/orwebsite/static/trees (@site/..., absolute-under-staticDirs, or path-relative references). Remote (http(s)://) image URLs are explicitly skipped (parseLocalURLPathreturns null for them and the function returns early).docusaurus build, invoked from Cloudflare Pages CI). There is no runtime/production code path —image-sizenever executes against a live request; there is no server here at all, just prebuilt static assets served by Cloudflare Pages..icns/.jxl/.heif/.heicfiles and found none. The vulnerable parsers are never invoked today.Net: the only way to trigger either bug would be for someone with write access to this repository to commit a malicious ICNS/JXL/HEIF file and reference it from a Markdown doc — which already requires repo write access (i.e., is not a remote or anonymous attack surface), and the worst case is a hung/timed-out CI build, not data exposure or code execution. Risk accepted pending an upstream fix; left unpatched. Will keep an eye on new
image-sizereleases (Dependabot will keep flagging this until one lands).Build verification
Both ran clean:
[SUCCESS] Generated static files in "build".— 174 docs processed,docusaurus-plugin-llmsgenerated its output files as usual, no new warnings or errors versus a baseline build.Verification that vulnerable versions are gone
npm auditdropped from 23 to 19 findings; the remaining 19 are allimage-sizeitself, the@docusaurus/*packages that transitively depend on it through@docusaurus/mdx-loader,docusaurus-plugin-llms(depends on@docusaurus/core), andbrowserslist(a separate advisory, not one of the seven in scope for this PR).Test plan
npm cifrom the committed lockfile succeedsnpm run buildsucceeds (includesprepare-docs.sh)npm lsconfirms all 5 patched packages resolve to fixed versionspackage.jsondiff is minimal (3 lines in theoverridesblock)package-lock.jsondiff touches only the 5 targeted package entries (verified via diff)