jfrog / jfrog/jfrog-cli-security
Npm jf scan issue
Open
Nobody has claimed this yet.
question
- Dominant language
- Go
- Stars
- 13
- Forks
- 50
- Avg merge
- 3d 48m
- Merged PRs (30d)
- 26
Description
JFrog Vulnerabilities are showed different between "jf audit" and "jf npm install with a jfrog build"
I don't know why. I need some help.
You can follow the operation steps in the following document to reproduce it.
Npm jf scan issue.docx
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 attached “Npm jf scan issue.docx” and follow its reproduction steps. Compare the vulnerabilities reported by jf audit with those from jf npm install using a JFrog build; done requires identifying why the results differ and documenting or correcting the discrepancy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100