I stumbled across this tool looking for a way to integrate output taken directly from bandit and other SWAMP supported-tools directly into CodeDX. I thought by converting it to SCARF, a CodeDX-compatible format, I could then pass input directly from these tools along to CodeDX.
After installing and attempting to run resultparser.pl it informs me that the --summary_file option must be set to point to an 'assessment_summary.xml' file. However nothing in this project's documentation explains the origin of this file, nor could I find anything in researching the topic. I could find no such file on my box for SWAMP which has performed several assessments, no options to download it via SWAMP's UI, nor any record of this filename in association with SWAMP or this repository on Google.
Knowing that the SCARF format includes some metadata about the project associated with the results it contains, I assume this file is required to provide that metadata. Given the critical nature of this file to the usage of this tool, I believe it would be helpful for the documentation or help menu to provide any insight into where this file is supposed to be generated.
I stumbled across this tool looking for a way to integrate output taken directly from bandit and other SWAMP supported-tools directly into CodeDX. I thought by converting it to SCARF, a CodeDX-compatible format, I could then pass input directly from these tools along to CodeDX.
After installing and attempting to run resultparser.pl it informs me that the --summary_file option must be set to point to an 'assessment_summary.xml' file. However nothing in this project's documentation explains the origin of this file, nor could I find anything in researching the topic. I could find no such file on my box for SWAMP which has performed several assessments, no options to download it via SWAMP's UI, nor any record of this filename in association with SWAMP or this repository on Google.
Knowing that the SCARF format includes some metadata about the project associated with the results it contains, I assume this file is required to provide that metadata. Given the critical nature of this file to the usage of this tool, I believe it would be helpful for the documentation or help menu to provide any insight into where this file is supposed to be generated.