Also I believe there's a JSON View available via the Marketplace.

To address the DCO requirement you'll need to sign-off the commit(s):

• https://github.com/zaproxy/zaproxy/blob/main/CONTRIBUTING.md#developer-certificate-of-origin
• https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff

Json formatting is excluded, DCO requirement is satisfied.

• The commits can be squashed or fixed-up, and signed off for DCO.
• The code formatting should be consistent. It is syntactically correct, and I'm sure there's other old code where things weren't done 'right' but conditionals should use curly braces even for single statements, etc.

Added null-checks for not yet implemented experimental DB case.
Added instance class checks before DB-related methods call.

New commits are squashed and signed off for DCO.
curly braces even for single statements - fixed

It seems that neglecting of special chars escaping for breaks UI may affect user workflow.
So I've reverted those changes.

updated header comments