JedWatson / JedWatson/react-select
Security Audit Failed Due to Moderate Vulnerability in @babel/runtime
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28k
- Forks
- 4.1k
- PR merge metrics
- No merged PRs in 30d
Description
We have encountered a security issue related to a vulnerable dependency in react-select. Our security audit failed due to the following moderate vulnerabilities:
Found Vulnerable Advisory Paths:
GHSA-968p-4wvh-cqc8 | react-select > @babel/runtime
GHSA-968p-4wvh-cqc8 | react-select > @emotion/react > @babel/runtime
GHSA-968p-4wvh-cqc8 | react-select > @emotion/react > @emotion/babel-plugin > @babel/runtime
GHSA-968p-4wvh-cqc8 | react-select > @emotion/react > @emotion/babel-plugin > babel-plugin-macros > @babel/runtime
GHSA-968p-4wvh-cqc8 | react-select > react-transition-group > @babel/runtime
GHSA-968p-4wvh-cqc8 | react-select > react-transition-group > dom-helpers > @babel/runtime
Security Advisory:
Steps to Reproduce:
Run yarn audit or npm audit in a project using react-select.
Observe that the security audit fails due to the above vulnerabilities.
Expected Behavior:
Security audit should pass without any vulnerabilities.
Actual Behavior:
Security audit fails with moderate severity vulnerabilities related to @babel/runtime.
Suggested Fix:
Upgrade dependencies in react-select that rely on outdated versions of @babel/runtime. If a fix is available in upstream dependencies, updating the relevant packages may resolve the issue.
Please advise on whether there is an existing fix or if a dependency update is planned in an upcoming release.
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running yarn audit or npm audit in a project using react-select and review the GHSA-968p-4wvh-cqc8 advisory paths listed in the issue. Trace the affected dependency versions and determine whether an upstream update is available; done means the audit no longer reports these @babel/runtime vulnerabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100