fix: vulnerable dep expr-eval-fork#371
Merged
six7 merged 1 commit intotokens-studio:mainfrom Dec 10, 2025
Merged
Conversation
🦋 Changeset detectedLatest commit: bc0d51c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
six7
approved these changes
Dec 10, 2025
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
2 participants
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.
@six7 it seems I have adopted expr-eval lib via a fork now and I've been getting a lot of security CVEs raised on it. Worked a fair bit with some of the security researchers behind it to get it fixed on my fork (since origin is fully abandoned).
I think a fair amount of the expr-eval-fork users are via sd-transforms actually, so this'll need a bump now that it's fixed.
Not sure if the NPM token is still valid, you may need to refresh it in NPM and update in this repo settings -> actions secrets
FYI: I also had NPM audit fix a couple of other vulnerable dev deps via pkg lock