caido-community
feat: add Leakz passive workflow
Please ensure your pull request adheres to the following guidelines:
- [x] Follow the same folder structure as other workflows (see https://github.com/caido/workflows/tree/main/convert)
- [x] Has a proper author name and workflow description
- [x] If using a 3rd party library, include its license as a comment in the source code.
Thanks for contributing!
Finally found time to check this out, looking forward to merging this one.
The workflow seems to be causing my CPU to go up to 100% + websites become super slow to load.
@dwisiswant0 Is that something you can improve on your end?
@Corb3nik - It seems my CPU isn't experiencing any excessive load, and just to note, I'm operating on Linux x86.
About the slow-loading sites you mentioned, I've noticed it too during my casual browsing. Ran some regression tests with projectdiscovery/katana, and all seems cool from my side. Can't figure out why it's acting up though, especially since it's just using the RegExp constructor.
The JS VM is not very performant/optimized, but I will start offloading the compute to other threads to relieve the proxy. Down the line plugins like those which are compute intensive should be moved to WASM so they run native bytecode instead of a VM.
Sorry we didnt get back to you faster @dwisiswant0 , before we can approve the merge we need a couple things:
- The original source code of the script node, I updated the Template to reflect that.
- If you want to add a source URL you can do so to reference your own Github project
- I updated the Template to reflect that.
Ok, then how can I include the compiled sources in the Workflow JSON?