Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jfrog audit scan command fails while finding existing packages #1107

Open
jashan05 opened this issue Jan 19, 2024 · 1 comment
Open

jfrog audit scan command fails while finding existing packages #1107

jashan05 opened this issue Jan 19, 2024 · 1 comment
Labels
question Further information is requested

Comments

@jashan05
Copy link

jashan05 commented Jan 19, 2024

Hello Team,

We are using jfrog audit scan using cli. It fails while running scan for a package which is a dependency of a dependency and is available in Artifactory. It seems it is not able to find that package. Could you please guide me on this.

Details:

16:53:38 [Info] Running SCA scan for yarn vulnerable dependencies in /azp/_work/1/s/CheckedOutSource directory...
16:53:38 [Info] Calculating Yarn dependencies...
16:53:39 [Warn] An error occurred while collecting dependencies info:
{"type":"warning","data":"Lockfile has incorrect entry for \"axios@^0.26.1\". Ignoring it."}
{"type":"error","data":"Couldn't find package \"axios@^0.26.1\" required by \"@nn-sls/core@^2.2.2\" on the \"npm\" registry."}

16:53:39 [Warn] An error was thrown while collecting dependencies info: exit status 1
Command output:
{"type":"info","data":"Visit https://yarnpkg.com/en/docs/cli/list for documentation about this command."}

Package in our Artifactory:

image

@jashan05 jashan05 added the question Further information is requested label Jan 19, 2024
@EyalDelarea
Copy link
Contributor

Hey @jashan05 ,

Could you please share some additional details that will help us investigate the issue?

  • Which version of Yarn are you using?
  • Share debug level logs (You can do that by exporting ENV var JFROG_CLI_LOG_LEVEL=DEBUG)
  • Share the package.json file if you can, or any other details you can to help us reproduce this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants