Skip to content

fix: bump axios to ^1.20.0 to resolve 13 Snyk findings - #153

Closed
cs-raj wants to merge 2 commits into
developmentfrom
fix/snyk-patch-deps-20261012
Closed

cs-raj wants to merge 2 commits into
developmentfrom
fix/snyk-patch-deps-20261012

Conversation

@cs-raj

@cs-raj cs-raj commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

Problem

Snyk reports 13 findings (8 high, 5 medium) on axios@1.18.1: ReDoS, SSRF, prototype pollution, confused deputy, input validation. All fixed in axios 1.20.0. This is a LIBRARY, so consumers resolve our ranges themselves and ^1.17.0 still allows the vulnerable version.

Fix

  • axios ^1.17.0 -> ^1.20.0 (raises the floor consumers see)
  • mocha ^11.7.1 -> ^11.8.0, mochawesome ^7.1.3 -> ^7.1.4 (dev deps flagged by npm audit)
  • Lock file regenerated; no overrides added
  • Version 1.5.4 -> 1.5.5

Remaining npm audit findings (46) are transitive under jest 28, babel 7 and nyc 15 and need major bumps; out of scope here.

Verification

Snyk 13 -> 0, npm audit 53 -> 46, npm run build passes on all four webpack targets.

Resolves DX-27818, DX-27819, DX-27820, DX-27821, DX-27822, DX-27823, DX-27824, DX-27825, DX-27826, DX-27827, DX-27828, DX-27829, DX-29401

🤖 Generated with Claude Code

Aravind-Kumar-cstk and others added 2 commits October 6, 2026 17:46
Lock file regenerated (fixed 13 snyk and 7 npm audit findings on its own).
Direct upgrades: axios ^1.17.0 -> ^1.20.0, mocha ^11.7.1 -> ^11.8.0, mochawesome ^7.1.3 -> ^7.1.4
Overrides: none
Vuln count: snyk 13 -> 0, npm audit 53 -> 46. Build verified passing.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@cs-raj
cs-raj requested review from a team as code owners October 12, 2026 10:03
@cs-raj cs-raj self-assigned this Oct 12, 2026
@snyk-io

snyk-io Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues
✅ Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@github-actions

Copy link
Copy Markdown

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 0 25 ✅ Passed
🟡 Medium Severity 0 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

✅ BUILD PASSED - All security checks passed

reeshika-h added a commit that referenced this pull request Nov 2, 2026
…ngelog

The previous commit brings in the dependency refresh from #153
(package-lock.json, mocha, mochawesome) alongside the axios and
follow-redirects fixes already in this PR.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@reeshika-h

Copy link
Copy Markdown
Contributor

Closing: the dependency commit from this PR (the package-lock refresh and the mocha/mochawesome bumps) is now included in #157, together with the axios 1.20.0 and follow-redirects 1.16.2 fixes. #157 targets main for the 02-11-2026 release, and its checks pass, including security-sca. Please reopen if anything from this PR is still needed separately.

🤖 Generated with Claude Code

@reeshika-h reeshika-h closed this Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants