-
Notifications
You must be signed in to change notification settings - Fork 9
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
scan failed to produce proper report
for repos without vulnerabilities
#11
Comments
I'm using the action with this repository which has no vulnerability. Or what did you mean by a clean repository? |
The error itself only shows up, when the json produced by govulncheck is not parseable, so it's likely that you misconfigured the path. There should be a info log telling you where and what it will scan |
Could you please double-check the logs and maybe attach them, with the given details I sadly can't do much investigating. |
If you (@Akaame ) use the |
Probably the issue is linked to the fact that the JSON Report Format was drastically changed. This should be fixed by #15 |
If issue still occurs and is not fixed after new release, feel free to create a new Issue. |
For this repo with no vulnerabilities the following error is printed out from the action:
ERR Scanning yielded error error="scan failed to produce proper report".
Would it be possible to check the action behavior for a clean repo?
The text was updated successfully, but these errors were encountered: