CMT-2285: add security audit report and update package dependencies#311
Draft
EvgeniiStepanishin wants to merge 1 commit into
Draft
CMT-2285: add security audit report and update package dependencies#311EvgeniiStepanishin wants to merge 1 commit into
EvgeniiStepanishin wants to merge 1 commit into
Conversation
size-limit report 📦
|
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.
Description
Ticket
Security audit of @staffbase/plugins-client-sdk dependency tree and remediation of all reported advisories via Yarn resolutions. Adds a SECURITY_AUDIT.md report documenting every advisory, its path, and the decision taken.
All 54 findings (4 High, 36 Moderate, 14 Low) were in devDependencies (build, test, and docs tooling) and all transitive. Runtime deps (loglevel, object.entries-ponyfill) had no advisories, and the published package ships only pre-built dist/, so none of these reach SDK consumers. Post-fix yarn audit reports 0 issues.
Related Issue
Motivation and Context
yarn audit surfaced 12 unique advisories across the dev toolchain (babel, rollup plugins, eslint, commitlint, jsdoc, jest tooling). Several are High severity (e.g. CVE-2026-44728 arbitrary code execution in @babel/plugin-transform-modules-systemjs, RCE in serialize-javascript). Pinning patched transitive versions removes the noise and keeps the build chain clean.
One nuance: the ajv fix had to be scoped to eslint/@eslint/eslintrc only. A global ajv resolution forced commitlint's @commitlint/config-validator (which needs ajv v8) down to v6, breaking the addKeyword API and the commit-msg hook. Scoping keeps eslint on patched ajv v6.15.0 while commitlint stays on ajv v8.20.0.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist:
Test plan: