Rick M
Rick M
Do you have instances where you wouldn't want them to be global? If so would you be good with them being tied to Context? (Similar to Alert Filters)
The best place to start is the Dev Guide 😄 https://www.zaproxy.org/docs/developer/
If it's complaining about Java 11 you're still on 2.15 because 2.16 requires Java 17.
Please don't ask questions as issues - the [ZAP User Group]( https://groups.google.com/group/zaproxy-users) is a much better place for questions.
The script should also be updated: 1) To have the Alert's name in title caps.
Okay, forgot 😉 Edited
Is vendors-[some-long-identifier].bundle.js.LICENSE.txt deployed on your web/app server?
Could you provide an example of `vendors-[some-long-identifier].bundle.js.LICENSE.txt ` that should be picked up? (Or from which a vuln library should be picked up.)
Probably better to remove unrelated commits, squash it all, and use rebase (vs merge) in the future
Thanks. For future reference you could have applied the changes to the existing branch/PR and just force pushed.