Repository navigation
Clear all open Dependabot alerts - #3
Merged
Merged
Conversation
npm audit went from 20 vulnerabilities (14 moderate, 6 high) to 0. - qs ^6.16.0 override — patches the DoS via attacker-controlled isBuffer and the array-limit bypass. Reached at runtime through @modelcontextprotocol/sdk -> express -> body-parser. - morgan ^1.12.1 override — patches log forging via unescaped Unicode line separators. Reached through appium-mcp -> appium-webdriveragent -> @appium/base-driver. - @puppeteer/browsers ^3.2.2 override — drops extract-zip (symlink path traversal / arbitrary file write, 6 high alerts, no patched release) in favour of modern-tar. v3 still exports every symbol @wdio/utils imports (install, canDownload, resolveBuildId, detectBrowserPlatform, computeExecutablePath, Browser, ChromeReleaseChannel), verified by importing webdriver and @wdio/utils against the overridden tree. - vitest / @vitest/coverage-v8 ^4.1.11 — patches the @vitest/mocker path traversal. Dev-only; the 3.x line has no fix. npm run build passes (109 tests) and npm ci resolves the lockfile under npm 10, which is what CI uses.
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.
Clears the 8 open alerts on https://github.com/testingbot/automation-mcp/security/dependabot.
npm auditgoes from 20 vulnerabilities (14 moderate, 6 high) to 0.What was flagged and what fixes it
qs^6.16.0morgan^1.12.1extract-zip@puppeteer/browsers^3.2.2vitest,@vitest/mocker^4.1.11All four are transitive except vitest; none are reachable by bumping a direct dependency, hence the overrides.
qs— DoS via attacker-controlledisBufferplus an array-limit bypass. Reached at runtime through@modelcontextprotocol/sdk→express→body-parser.morgan— log forging via unescaped Unicode line separators. Reached throughappium-mcp→appium-webdriveragent→@appium/base-driver.extract-zip— symlink path traversal / arbitrary file write, the source of all 6 high alerts, and it has no patched release.@puppeteer/browsers3.x drops it in favour ofmodern-tar, so overriding the parent is the only available fix. The consumer iswebdriver→@wdio/utils→@puppeteer/browsers; v3 still exports every symbol@wdio/utilsimports (install,canDownload,resolveBuildId,detectBrowserPlatform,computeExecutablePath,Browser,ChromeReleaseChannel). Verified by importingwebdriverand@wdio/utilsagainst the overridden tree —startWebDriverresolves and the eager@puppeteer/browsersimport inside@wdio/utils/nodeloads cleanly.vitest— path traversal / arbitrary file read via the mocker's redirect mock. Dev-only, and the 3.x line has no fix, so this is a major bump to 4.1.11. Test suite and coverage run unchanged.Verification
npm run build(lint + format:check + 109 tests + tsc) passes.npm run test:coverageproduces the same coverage numbers under vitest 4.npm ci --allow-git=allresolves the lockfile under npm 10, which is what the test workflow uses on Node 20 and 22.One local note: adding vitest 4 with
npm installunder npm 10 trips a known arborist bug (Cannot read properties of null (reading 'edgesOut')) on vitest 4's optional peer graph. The lockfile here was generated with npm 11.npm ciis unaffected, so CI and the release workflow (which installsnpm@latest) are fine, but contributors regenerating the lockfile on npm 10 may neednpx npm@11 install.