Simon Bennetts

That and * https://www.zaproxy.org/docs/api/#spiderviewallurls * https://www.zaproxy.org/docs/api/#spiderviewaddednodes (which wont give you what you want)

For example, taking the [Passive scan rules (alpha)](https://www.zaproxy.org/docs/desktop/addons/passive-scan-rules-beta/) rules you would need to: - Edit all of the rule classes in [pscanrulesAlpha](https://github.com/zaproxy/zap-extensions/tree/main/addOns/pscanrulesAlpha/src/main/java/org/zaproxy/zap/extension/pscanrulesAlpha) to add the `getHelpLink()` method mentioned above -...

Oh, my bad - I mixed up the add-ons, I'll correct that now..

Comment corrected, I've added your name to the add-on in the first comment and yes, you are right about the Base64 Disclosure changes 😁

It makes it easier for us to find the other constructors - if we always use the new ones then we can spot the ones that dont use them much...

No surprise there, its the same underlying code 😁

Yeah, it does look like these should be the same type of alerts, even though the detection code is slightly different. This would require a code change. Thoughts @thc202 @kingthorin...

Yeah, latest plan is to change the core interfaces, but I'll aim to implement the method for the rules in the first comment and we can see how well it...

Yeah - thats what I meant by the i18n part - in case we need to introduce new more generic strings.

Example of what one of the rules which raises multiple alerts would look like. Currently its mostly blank :/ https://www.zaproxy.org/docs/alerts/10020/