Repository navigation
fix(deps): override papaparse to ^5.7.1 and apply npm audit fix (+Claude) - #288
dhruv-parekh-cs wants to merge 1 commit into
Conversation
papaparse@5.7.0 (SNYK-JS-PAPAPARSE-22566253, High) arrives through @contentstack/cli-utilities@2.0.2, already the latest release, which declares papaparse ^5.5.4. 5.7.1 is inside that range, so an override of ^5.7.1 floors the fix without forcing a new major on the parent and without relying on the lockfile alone. Also commits the lockfile changes from npm audit fix (no --force): semver-compatible bumps of typescript-eslint, oclif, ts-jest, picomatch, @rollup/plugin-typescript and others. The libc fields that npm 10 drops from platform-specific optional packages are kept as they were. #claude_code# 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NTFwVt4WF1HMWWtmwmLxYL
✅ 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
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
dhruv-parekh-cs
left a comment
There was a problem hiding this comment.
Reviewed the whole PR: 0 high, 0 medium, 1 low (inline).
Cross-repo (snyk-fix 18-Nov-2026 batch): no issues; the 10 PRs are independent dependency bumps with no shared contract or deploy order.
Not approved: this is the owner's own PR.
— 🤖 launch-pr-review-agent (Claude)
Generated by Claude Code
| "minimatch": "^11.0.1" | ||
| } | ||
| }, | ||
| "papaparse": "^5.7.1" |
There was a problem hiding this comment.
Low The papaparse override only applies when launch-cli is the root project; it is not shipped to people who install @contentstack/cli-launch.
npm ignores overrides in a dependency's package.json, and no npm-shrinkwrap.json is generated or published (it's listed in files, but nothing creates it). A csdx user whose lockfile already holds papaparse 5.7.0 under @contentstack/cli-utilities (^5.5.4) keeps 5.7.0 after upgrading the plugin. Only this repo's own install and Snyk scan go clean.
Fix: raise the papaparse floor in @contentstack/cli-utilities, or generate and ship the shrinkwrap; otherwise word the commit/PR as a repo-scan fix only.
Generated by Claude Code
There was a problem hiding this comment.
needs-human. Confirmed: npm ignores overrides in an installed dependency, @contentstack/cli-utilities 2.0.0–2.0.2 all declare papaparse ^5.5.4, and nothing in the repo creates npm-shrinkwrap.json (release.yml only runs npm ci and npm publish). So this override fixes the repo's own lockfile and Snyk scan, not consumers of @contentstack/cli-launch.
A launch-cli maintainer needs to pick one of these:
- (a) Get a cli-utilities release with
papaparse ^5.7.1from the cli-utilities owners, then bump it here. - (b) Generate and publish the shrinkwrap. This changes release behaviour.
- (c) Keep the override, and reword the PR description and squash-merge message as a repo-scan fix only.
I'm leaving this thread open until someone picks.
— 🤖 snyk-fix follow-up (Claude)
Generated by Claude Code
Summary
Automated snyk-fix sweep, 18-Nov-2026,
depstrack. Base:development.This PR fixes one High Snyk finding (papaparse) and commits the lockfile changes from
npm audit fix(run without--force). Two findings carried over from earlier runs are still open (see Needs human review).papaparse(transitive:@contentstack/cli-utilities@2.0.2 > papaparse)"papaparse": "^5.7.1")@contentstack/cli-utilities@2.0.2is already the latest release and declarespapaparse ^5.5.4. A lockfile refresh alone would resolve 5.7.1, but that range still allows 5.7.0, so the fix would last only until the lockfile changes. The caret override sets a floor at the patched release and stays inside the parent's declared major.Ecosystem-native audit (
npm audit fix, no--force)@typescript-eslint/*andtypescript-eslint8.63.0 → 8.73.0,eslint-config-oclif6.0.176 → 6.0.179,oclif4.23.27 → 4.24.0,@oclif/plugin-not-found3.2.88 → 3.3.0,@oclif/plugin-warn-if-update-available3.1.68 → 3.2.0,ts-jest29.4.11 → 29.4.15,@rollup/plugin-typescript12.3.0 → 12.3.1,@rollup/pluginutils5.4.0 → 5.5.1,picomatch4.0.5 → 4.0.7,minimatch10.2.5 → 10.2.6,nyc/node_modules/glob13.0.6 → 13.0.7.typescript-estreenow gets its ownminimatch@11.0.9, outside the advisory range.snyk testdoes not report them):picomatch<=4.0.7 (GHSA-fc5q-39xc-vjpf, high): no fix published. 4.0.7 is the latest release. This one advisory accounts for most of the 64 "high" counts (jest, rollup plugins, eslint tooling, tinyglobby).minimatch>=7.0.0 <11.0.1 (GHSA-g3hv-75wg-m249, moderate) at 10.2.6 / 9.0.9 / 5.1.9 underglob@13,glob@10,test-excludeandfilelist. Clearing it means forcing minimatch 11 onto parents that declare ^10, ^9 or ^5, which is a breaking change.glob>=9.0.0 <=14.0.1 (GHSA-3g3m-2fjr-6pw4, moderate) at 13.0.7 / 10.5.0 undernycand others. The only fix is a major version bump.libcfield from platform-specific optional packages (@rollup/rollup-linux-*and similar). Those fields were restored as they are ondevelopment, so the diff shows only real version changes.npm ciaccepts the lockfile as committed.Retired overrides
None. Each existing override was checked against the declared range of every dependent that pulls the package in. Each dependent's range still allows a vulnerable version, so every override is still needed:
qs:body-parser@1.20.9declares~6.16.0;@contentstack/management@1.31.2declares^6.16.0.follow-redirects:axios@1.20.0declares^1.16.0.tty-table > csv:tty-table@4.2.4declares^5.5.3.tmp:external-editor@2.2.0declares^0.0.33.serialize-javascript:mocha@11.8.0declares^6.0.2.diff:mochaandsinondeclare^7.0.0;ts-nodedeclares^4.0.1.@oclif/core > minimatch:@oclif/core@4.14.0declares^10.2.5.Dashboard-only artifacts
None.
Needs human review (not yet resolved)
open@8.4.2, pulled in through@contentstack/cli-utilities@2.0.2(and through@contentstack/cli-command@2.0.2 > cli-utilities). The fix is open 11.0.0. cli-utilities is at its latest release and declaresopen ^8.4.2, so an override would force a new major (open 11 is ESM-only) onto a library this repo doesn't control. The real fix is a cli-utilities release that moves to open 11. launch-cli's own directopendependency is already on ^11 (fix(deps): upgrade open to 11 and @oclif/core to 4.14 to clear Snyk findings #286).adm-zip@0.6.1(direct). Every version is affected and there is no fix. 0.6.1 is the latest release.Workflows
No runtime version changed, so nothing under
.github/workflows/needed to be synced.Code review
One pass (
/code-review, Opus 5.5, high effort, overorigin/development...CL-snyk-fixes/18-Nov-2026): the/code-reviewgate found no High or Medium findings. No changes were made after the review, and nothing was moved to needs human review.Validation
npm ciwith the committed lockfile: OK.npm run build: passed.npm test(mocha unit tests, jest 142/142, jest integration 33/33): passed.npm run lint: 59 errors, the same 59 as on an untouchedorigin/developmentcheckout. None come from this change.snyk test --all-projects(1 project,package-lock.json, matching the singlepackage.json): SNYK-JS-PAPAPARSE-22566253 no longer appears. Only the two needs-human-review findings above remain.Warnings
None from
npm installbeyond the existing audit summary.#claude_code#
Generated by Claude Code