Repository navigation
Conversation
Vulnerable Libraries (1)
More info on how to fix Vulnerable Libraries in JavaScript. 👉 Go to the dashboard for detailed results. 📥 Happy? Share your feedback with us. |
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.
Superseded by #59 after correcting the ticket and branch to SYN-674.
Follow-up to #31 for SYN-674. The remaining findings are in the example app's Create React App dependency tree and the root esbuild dependency. Both lockfile audits now report zero vulnerabilities.
Approach
Move the example to Vite because npm offers no compatible fixes for several remaining Create React App dependency chains. Keep the published library at 2.1.0, the React peer links, the existing API key environment variable, port 3000, and the
buildoutput folder. The six example source files are renamed to.jsxwith identical contents, and lint includes the new extensions. The example now requires Node 20.19+ or 22.12+.Use a scoped override to update tsup's esbuild dependency to 0.28.2 for the remaining low-severity advisory. The library build continues to use tsup, and the CI workflow is unchanged.
Validation
Security scan follow-up
GuardRails flags a medium-severity finding for ESLint 8.57.1, which is unchanged from main. Its recommended upgrade to 9.26.0 matches CVE-2025-50537, an advisory GitHub withdrew on February 3, 2026 because it concerns development-time rule testing. The advisory ID still needs confirmation in GuardRails before resolving the finding.