Is your feature request related to a problem? Please describe.
Working with multiple outputs in a single repository has been a pain in the ass. It gets worse when you have to maintain multiple rules and rulesets.
Describe the solution you'd like
At this point, I'd rather a separate repository for the following parts:
- Assets used by HTML report
- Rules and rulesets (plain-text JSON files)
e.g. silverhack/monkey365, silverhack/monkey365-assets, silverhack/monkey365-rules. Since I'm not an organisation (Monkey365 is maintained by one developer) it wouldn't make be hard to organize/find repos either.
Additional context
A separate repository would potentially make it more cumbersome to coordinate updates to all the core, HTML assets and the rules at once, but also would help to better maintain repositories for potential updates, rewording findings, unused dependencies, etc..
Is your feature request related to a problem? Please describe.
Working with multiple outputs in a single repository has been a pain in the ass. It gets worse when you have to maintain multiple rules and rulesets.
Describe the solution you'd like
At this point, I'd rather a separate repository for the following parts:
e.g. silverhack/monkey365, silverhack/monkey365-assets, silverhack/monkey365-rules. Since I'm not an organisation (Monkey365 is maintained by one developer) it wouldn't make be hard to organize/find repos either.
Additional context
A separate repository would potentially make it more cumbersome to coordinate updates to all the core, HTML assets and the rules at once, but also would help to better maintain repositories for potential updates, rewording findings, unused dependencies, etc..