Repository navigation
fix(deps): upgrade open to 11 and override papaparse to 5.7.1 to clear Snyk findings - #289
Merged
Merged
Conversation
…r Snyk findings
The pre-commit `snyk test --fail-on=all` started failing on v2-dev with
two new High findings:
- open@8.4.2 (SNYK-JS-OPEN-22112123), fixed in open@11.
- papaparse@5.5.4 via @contentstack/cli-utilities@2.0.2
(SNYK-JS-PAPAPARSE-22566253), fixed in 5.7.1; cli-utilities 2.0.2 is
the latest, so it is pinned with an override.
open@11 is ESM-only. A static import compiles to require("open"), which
crashes on Node 22.0-22.11 (still allowed by engines >=22.0.0), so
openInBrowser now loads it lazily through a Function-built import(),
matching V1's #286. It returns its promise so its tests can await the
swallowed failures, and a loader test covers the real dynamic import.
The integration suites that mocked 'open' now route src/core/browser
through test/support/browser.ts, which runs the real openInBrowser
against the mocked module, so no test launches a real browser. The
.talismanrc checksums for package.json and the three edited integration
suites are refreshed for these changes.
Left as is: adm-zip@0.6.1 and cli-utilities' own open@8 have no upgrade
path, so they do not fail --fail-on=all.
#claude_code#
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <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
ℹ️ 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 |
siddharth-kulkarni-cs
approved these changes
Nov 18, 2026
chhavi-mandowara-cstk
approved these changes
Nov 18, 2026
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.
What
open8.4.2 → 11.0.4 (SNYK-JS-OPEN-22112123, High).papaparseto ^5.7.1 under@contentstack/cli-utilities@2.0.2, the latest release (SNYK-JS-PAPAPARSE-22566253, High).openInBrowsernow loads the ESM-onlyopen@11through a Function-builtimport(), the same approach as V1's fix(deps): upgrade open to 11 and @oclif/core to 4.14 to clear Snyk findings #286. A static import compiles torequire("open"), which crashes on Node 22.0–22.11, still allowed byengines(>=22.0.0).opennow routesrc/core/browserthroughtest/support/browser.ts, which runs the realopenInBrowseragainst the mocked module, so no test opens a real browser..talismanrcchecksum forenvironments-create.test.tsis refreshed for its one-line change.Not fixable here:
adm-zip@0.6.1and theopen@8thatcli-utilitiespulls in have no upgrade path, so they don't failsnyk test --fail-on=all.Both findings currently fail the pre-commit Snyk hook on
v2-dev. This PR unblocks CL-8788 (deployments:cancel400 message), which follows once this merges.Tests
npm test: 193 suites / 3818 tests pass.browser.tsis 100% covered, including a test that loads the realopen@11.npm run lint,tsc --noEmitand the build pass. The builtdist/core/browser.jsloadsopen@11at runtime.snyk test --all-projects --fail-on=allpasses, and so does the pre-commit hook (lint-staged, Talisman, trufflehog, Snyk).#claude_code#
🤖 Generated with Claude Code