npm audit issue for @commitlint/config-conventional (dot-prop)
See original GitHub issueWe have encountered an npm audit issue regarding @commitlint/config-conventional
It is understood that the version fix is already in master but is yet to be published. https://github.com/conventional-changelog/commitlint/commit/44144ca7ac2b8e748e717f2dc6be2c5b1ea1f124
Expected Behavior
Has no/low npm audit issue.
Current Behavior
Version 9.1.2 is having the npm audit issue.
Affected packages
- cli
- core
- prompt
- config-angular
Possible Solution
Steps to Reproduce (for bugs)
- First step
- Second step
commitlint.config.js
```js ```Context
Affecting our CI flow with npm audit checks. The advisory was published 29 July 2020.
Your Environment
Executable | Version |
---|---|
commitlint --version |
VERSION |
git --version |
VERSION |
node --version |
10.16.0 |
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:9
Top Results From Across the Web
Facing vulnerability security issue for dot-prop when updating ...
After updating npm to the latest, I ran npm audit and got two vulnerabilities for the dot-prop package dependency which is showing under...
Read more >dot-prop - npm
Get, set, or delete a property from a nested object using a dot path. Latest version: 7.2.0, last published: 10 months ago.
Read more >npm audit: Broken by Design - Overreacted
1 vulnerabilities (0 moderate, 1 high) To address issues that do not require attention, run: npm audit fix To address all issues (including ......
Read more >Resolve NPM security vulnerabilities - Payam Mousavi - Medium
It says, the dot-prop package has a security issue which needs to get fixed, ... But if you run npm audit fix you'll...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We’ll switch
next
tolatest
soon and create a newnext
from current master.This duplicates/relates to #2032 (Edit: it does not)
Thank you 😃 looking forward to it 😃