Repository navigation
fix: bump 2 deps to resolve Snyk vulnerabilities - #191
Open
pradyumna-garg-contentstack wants to merge 1 commit into
Open
pradyumna-garg-contentstack wants to merge 1 commit into
pradyumna-garg-contentstack wants to merge 1 commit into
Conversation
Lock file regenerated (fixed 25 on its own). Direct upgrades: axios ^1.7.9 -> ^1.21.0 (dependencies), @babel/core ^7.2.2 -> ^7.29.7 (devDependencies) Added devDependency: @types/node ^25.6.0 (keeps the TypeScript 4.7 build working; dev-only) Overrides: none Vuln count: snyk 25 -> 0, npm audit 31 -> 9. Build verified passing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
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.
Problem
Snyk reports 25 vulnerabilities (8 high, 17 medium) in the committed
package-lock.jsononmain: 22 in axios 1.16.0, 2 in follow-redirects 1.16.0 and 1 in form-data 4.0.5. npm audit reports 31 (3 critical, 14 high, 7 moderate, 7 low).Fix
This repo is a LIBRARY (
@contentstack/app-sdkon npm). Consumers never see our lock file; they resolve ourpackage.jsonranges themselves, so the floors had to go up inpackage.json:axios^1.7.9→^1.21.0independencies. The axios floor is raised so consumers can't resolve a vulnerable axios; this clears all 22 axios findings. axios 1.21.0 also requiresform-data ^4.0.6, the fixed version.@babel/core^7.2.2→^7.29.7(devDependency; clears an npm audit low).@types/node^25.6.0added as a devDependency, so TypeScript 4.7 can build. A fresh lock otherwise resolves@types/node26 through jest's*range, TypeScript 4.7 can't parse it, and thepreparebuild fails. It is dev-only and doesn't affect consumers.package-lock.jsonregenerated: follow-redirects 1.16.2 and form-data 4.0.6. No overrides, no version bump.Verification
Snyk 25 → 0, npm audit 31 → 9.
npm run build(webpack) passes, andnpm testpasses 249/249. ggshield was run by hand on the staged diff (no secrets found), because the repo's local huskycore.hooksPathbypasses the global ggshield hook.What remains
follow-redirects ^1.16.0. A consumer's fresh install gets 1.16.2, but a consumer lock pinned to 1.16.0/1.16.1 needs a refresh.__test__/stackUtils.test.ts) are source-level and out of scope.Jira: DX-20981, DX-20982, DX-20983, DX-20984, DX-20985, DX-20986, DX-20987, DX-20988, DX-20989, DX-20990, DX-20991, DX-27758, DX-27759, DX-27760, DX-27761, DX-27762, DX-27763, DX-27764, DX-27765, DX-27766, DX-27767, DX-27768, DX-30482, DX-30483
🤖 Generated with Claude Code