Vulnerability with dependencies
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 193
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
I'm getting these problems when suing the module. Not sure if it can be fixed by just updating to the latest modules or that would break something.
> Manual Review
> Some vulnerabilities require your attention to resolve
>
> Visit https://go.npm.me/audit-guide for additional guidance
>
>
> High Regular Expression Denial of Service
>
> Package minimatch
>
> Patched in >=3.0.2
>
> Dependency of tokml
>
> Path tokml > strxml > tap > glob > minimatch
>
> More info https://nodesecurity.io/advisories/118
>
>
> Low Incorrect Handling of Non-Boolean Comparisons During
> Minification
>
> Package uglify-js
>
> Patched in >= 2.4.24
>
> Dependency of tokml
>
> Path tokml > strxml > tap > runforcover > bunker > burrito >
> uglify-js
>
> More info https://nodesecurity.io/advisories/39
>
>
> Low Regular Expression Denial of Service
>
> Package uglify-js
>
> Patched in >=2.6.0
>
> Dependency of tokml
>
> Path tokml > strxml > tap > runforcover > bunker > burrito >
> uglify-js
>
> More info https://nodesecurity.io/advisories/48
>
> found 3 vulnerabilities (2 low, 1 high) in 3335 scanned packages
> 3 vulnerabilities require manual review. See the full report for details
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 with the npm audit report in the issue and trace the tokml dependency paths through strxml, tap, glob, runforcover, bunker, burrito, and minimatch or uglify-js. Check the project's dependency manifests and available compatible updates, then run the existing test suite and npm audit; done means the reported vulnerabilities are resolved without breaking tokml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100