Replies: 3 comments 3 replies
-
|
failOpen was kind enough to note in Discord that I didn't provide a target. With one however, I get similar results. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@tibbon I think that is because there are no results, as it says:
When there are results, there is a sarif file created: |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
This discussion closed automatically due to inactivity. Feel free to reopen or start new if still relevant. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Nuclei version:
3.1.10
Current Behavior:
No sarif file is output when I expect there to be one. This is happening locally on my Mac, and with GitHub Actions
Expected Behavior:
When I run nuclei with the
-se nuclei.sarifflag, I expect a valid sarif file to be present at the end of the testsSteps To Reproduce:
Other flags to output files like
-me markdown_exampleor-je json_exampleappear to work properly and write a file with valid content. The-se nuclei.sarifdoes not appear to.Anything else:
I've tried to read through the Golang code (not my strongest), dug around in issue trackers, checked in the GitHub action, and I can't seem to find anything. I'm wondering if there's something non-obvious about the type of examples that I'm running against, and their output?
Beta Was this translation helpful? Give feedback.
All reactions