You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
osv-scanner --lockfile=release/app/package-lock.json no longer reports those advisories after the update
npm ci in release/app installs cleanly with the update; tar-fs@2.1.4 pack/extract roundtrip smoke test passes. The repo's jest setup has no tests in release/app (exits 0 with no tests on this lockfile path).
Note: osv-scanner still reports separate advisories in this lockfile (ws@8.18.0, brace-expansion, and others). This patch only clears the two tar-fs advisories.
Scope: lockfile update only, tar-fs entry in release/app/package-lock.json.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You have signed the CLA already but the status is still pending? Let us recheck it.
release/app/package-lock.json is excluded by !**/package-lock.json
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
🔍 Trigger review
Comment @coderabbitai help to get the list of available commands.
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
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.
Updates
tar-fsto address GHSA-8cj5-5rvv-wf4v and GHSA-vj76-c3g6-qr5v.Evidence:
release/app/package-lock.jsonreferencedtar-fs@2.1.2osv-scannerreported GHSA-8cj5-5rvv-wf4v, GHSA-vj76-c3g6-qr5v before the updatetar-fs@2.1.4Validation:
osv-scanner --lockfile=release/app/package-lock.jsonno longer reports those advisories after the updatenpm ciinrelease/appinstalls cleanly with the update;tar-fs@2.1.4pack/extract roundtrip smoke test passes. The repo'sjestsetup has no tests inrelease/app(exits 0 with no tests on this lockfile path).Note:
osv-scannerstill reports separate advisories in this lockfile (ws@8.18.0,brace-expansion, and others). This patch only clears the twotar-fsadvisories.Scope: lockfile update only,
tar-fsentry inrelease/app/package-lock.json.