Hey Brandon! You’re spot on, these two workflows share the
!lookup-vuln trigger command.
When planning these workflows, we thought it made more sense to “overload” this trigger so both workflows would run if they are both active. One is not meant to be a replacement of the other; rather, they’re meant to be complementary.
A couple of reasons we didn’t combine these into one workflow:
- By making them separate workflows, they can run in parallel rather than sequentially
- As with all the workflow templates we put out there, our goal is to provide immediate value but also give workflow builders a jumping-off point for more advanced or custom use cases.
If someone took the time to combine these two workflows into one that performs both the vulnerability and the exploit lookup, and that someone felt inspired enough to contribute it back to us, then we would be more than happy to post it to the extension library and shower that someone with thanks, praise, and forum badges!!