Fix all npm audit advisories (0 vulnerabilities)#211
Merged
Conversation
Clears all 12 advisories reported by `npm audit` (was: 4 critical, 4 high,
3 moderate, 1 low). All fixes were applied with `--min-release-age=7` so no
version published within the last 7 days is pulled in (supply-chain cooldown).
Consumer-facing (production transitive) deps:
- form-data 4.0.5 -> 4.0.6 (CRLF injection, via axios)
- ws 8.x -> 8.21.0 (mem disclosure / DoS, via socket.io-client)
- engine.io-client -> 6.6.6 (pulled patched ws)
Dev-only tooling (no consumer impact):
- vitest + @vitest/ui + @vitest/coverage-{v8,istanbul} 1.6.1 -> 4.1.9
(UI server arbitrary file read/exec; pulls patched vite/vite-node/esbuild)
Test suite (172 tests) and type checks pass on vitest 4.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
🚀 Package Preview Available!Install this PR's preview build with npm: npm i @base44-preview/sdk@0.8.34-pr.211.0879225Prefer not to change any import paths? Install using npm alias so your code still imports npm i "@base44/sdk@npm:@base44-preview/sdk@0.8.34-pr.211.0879225"Or add it to your {
"dependencies": {
"@base44/sdk": "npm:@base44-preview/sdk@0.8.34-pr.211.0879225"
}
}
Preview published to npm registry — try new features instantly! |
carmelc
approved these changes
Jun 29, 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.
What
Clears all 12 advisories reported by
npm audit— from 4 critical / 4 high / 3 moderate / 1 low down to 0 vulnerabilities.Every fix was applied with
--min-release-age=7, so no version published within the last 7 days is pulled in (supply-chain cooldown — avoids the window when a freshly-compromised release is most likely live).Changes
Consumer-facing (production transitive deps — these reach apps using the SDK):
form-datawsengine.io-clientwsDev-only tooling (no consumer impact —
devDependencies, never shipped):vitest,@vitest/ui,@vitest/coverage-v8,@vitest/coverage-istanbulvite,vite-node,esbuildOnly
package.json+package-lock.jsonchange.Verification
npm audit→ found 0 vulnerabilitiesnpm test(type checks + 172 unit tests) → all pass on vitest 4Notes
1 → 4major is a devDependency bump only; it does not affect the published package or its consumers. Tests pass unchanged; vitest 4 emits two non-fatal deprecation warnings (a non-top-levelvi.mockintests/unit/analytics.test.ts, and the now-ignoredesbuildblock invitest.config.tssince v4 uses oxc) — cosmetic, left for a follow-up.🤖 Generated with Claude Code