[BUG] npm audit does not show the package from package.json that depends on the vulnerable package
Open
Nobody has claimed this yet.
Bug
Priority 2
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
npm audit does not output which of the packages from the package.json dependencies depends on the detected vulnerable package(s).
Expected Behavior
npm should tell me which of the packages I'm using depend(s) on the vulnerable package(s), so that I can update or replace it/them.
Steps To Reproduce
git clone https://github.com/dandv/npm-audit-bug.git && cd npm-audit-bugnpm installnpm audit- Notice the output doesn't mention which of the user's packages from
package.jsondepends on the vulnerable package.
Environment
- npm: 10.6.0
- Node.js: 18.19.0
- OS Name: Fedora Linux 38
- npm config:
; "global" config from /etc/npmrc
; prefix = "/usr/local" ; overridden by user
python = "/usr/bin/python3"
; "user" config from /home/dandv/.npmrc
prefix = "/home/dandv/.local"
; node bin location = /usr/bin/node-18
; node version = v18.19.0
; npm local prefix = /home/dandv/prg/npm-audit-bug
; npm version = 10.6.0
; cwd = /home/dandv/prg/npm-audit-bug
; HOME = /home/dandv
; Run `npm config ls -l` to show all defaults.
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
Reproduce the report with the linked dandv/npm-audit-bug project by running npm install and npm audit, then trace how npm audit formats dependency vulnerability output. Done means the output identifies which package.json dependency leads to each vulnerable package; validate the result against the reproduction project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- devtools, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100