Skip to content

fix(deps): override papaparse to ^5.7.1 and apply npm audit fix (+Claude) - #288

Open
dhruv-parekh-cs wants to merge 1 commit into
developmentfrom
CL-snyk-fixes/18-Nov-2026
Open

dhruv-parekh-cs wants to merge 1 commit into
developmentfrom
CL-snyk-fixes/18-Nov-2026

Conversation

@dhruv-parekh-cs

Copy link
Copy Markdown
Contributor

Summary

Automated snyk-fix sweep, 18-Nov-2026, deps track. 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).

Issue Severity Package Before → after Bucket Rationale
SNYK-JS-PAPAPARSE-22566253 High papaparse (transitive: @contentstack/cli-utilities@2.0.2 > papaparse) 5.7.0 → 5.7.1 Override ("papaparse": "^5.7.1") @contentstack/cli-utilities@2.0.2 is already the latest release and declares papaparse ^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)

  • Before: 69 advisories (10 moderate, 59 high), counted by package. After: 69 (5 moderate, 64 high). None of the three root advisories cleared, so the package count did not change. Most of the remainder comes from one root advisory that has no fix (picomatch, below).
  • Semver-compatible bumps it applied (lockfile only): @typescript-eslint/* and typescript-eslint 8.63.0 → 8.73.0, eslint-config-oclif 6.0.176 → 6.0.179, oclif 4.23.27 → 4.24.0, @oclif/plugin-not-found 3.2.88 → 3.3.0, @oclif/plugin-warn-if-update-available 3.1.68 → 3.2.0, ts-jest 29.4.11 → 29.4.15, @rollup/plugin-typescript 12.3.0 → 12.3.1, @rollup/pluginutils 5.4.0 → 5.5.1, picomatch 4.0.5 → 4.0.7, minimatch 10.2.5 → 10.2.6, nyc/node_modules/glob 13.0.6 → 13.0.7. typescript-estree now gets its own minimatch@11.0.9, outside the advisory range.
  • What it declined (all reach the tree only through devDependencies or build tooling, so snyk test does 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 under glob@13, glob@10, test-exclude and filelist. 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 under nyc and others. The only fix is a major version bump.
  • Lockfile note: npm 10 removes the libc field from platform-specific optional packages (@rollup/rollup-linux-* and similar). Those fields were restored as they are on development, so the diff shows only real version changes. npm ci accepts 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.9 declares ~6.16.0; @contentstack/management@1.31.2 declares ^6.16.0.
  • follow-redirects: axios@1.20.0 declares ^1.16.0.
  • tty-table > csv: tty-table@4.2.4 declares ^5.5.3.
  • tmp: external-editor@2.2.0 declares ^0.0.33.
  • serialize-javascript: mocha@11.8.0 declares ^6.0.2.
  • diff: mocha and sinon declare ^7.0.0; ts-node declares ^4.0.1.
  • @oclif/core > minimatch: @oclif/core@4.14.0 declares ^10.2.5.

Dashboard-only artifacts

None.

Needs human review (not yet resolved)

  • SNYK-JS-OPEN-22112123 (High): 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 declares open ^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 direct open dependency is already on ^11 (fix(deps): upgrade open to 11 and @oclif/core to 4.14 to clear Snyk findings #286).
  • SNYK-JS-ADMZIP-21707815 (Medium): 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, over origin/development...CL-snyk-fixes/18-Nov-2026): the /code-review gate found no High or Medium findings. No changes were made after the review, and nothing was moved to needs human review.

Validation

  • npm ci with 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 untouched origin/development checkout. None come from this change.
  • snyk test --all-projects (1 project, package-lock.json, matching the single package.json): SNYK-JS-PAPAPARSE-22566253 no longer appears. Only the two needs-human-review findings above remain.

Warnings

None from npm install beyond the existing audit summary.

#claude_code#


Generated by Claude Code

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
@dhruv-parekh-cs
dhruv-parekh-cs requested a review from a team as a code owner November 18, 2026 05:01
@snyk-io

snyk-io Bot commented Nov 18, 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 2 25 ✅ Passed
🟡 Medium Severity 0 1 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

ℹ️ 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:

  • Critical without fixes: 0
  • High without fixes: 2
  • Medium without fixes: 1
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@dhruv-parekh-cs dhruv-parekh-cs left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Comment thread package.json
"minimatch": "^11.0.1"
}
},
"papaparse": "^5.7.1"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.1 from 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

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

⌂ Proxy