react-component / react-component/input-number
48 high security risk vulnerabilities reported by `npm audit` (input-number v4.5.0)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 323
- Forks
- 188
- Avg merge
- 20h 3m
- Merged PRs (30d)
- 1
Description
Repro steps:
- Fork the repo and clone it
- Run
npm install - Run
npm audit
You will see the output reports found 108 vulnerabilities (26 low, 33 moderate, 48 high, 1 critical)
This is on version 4.5.0 of the library.
To fix this, you can run npm audit fix. Note: This could potentially include major version dependency updates that include breaking changes that will need to be resolved.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the report by running npm install followed by npm audit, as described in the issue. Review the dependency metadata and the changes proposed by npm audit fix, then verify that the reported vulnerabilities are resolved without introducing the breaking changes noted in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100