Repository navigation
chore: audit only runtime dependencies - #101
Merged
Merged
Conversation
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.
npm auditfails on two advisories in development tools, which blocksprepublishOnlyand every release: GHSA-g3hv-75wg-m249 inminimatch(through ESLint) and GHSA-8g5g-mxqh-grgj invite. Neither ships in the package, and ESLint 10.14 still depends on the affectedminimatch, so there is no upstream fix.npm audit --omit=devfinds 0 vulnerabilities in the runtime dependencies.npm run checknow audits runtime dependencies only. Development tools should be audited again once ESLint moves tominimatch11.Validation:
npm run check.