Rule `jenkins/unsafe-classes` resolves class paths against repository root

[NotMyFault]

It appears, the unsafe-classes rule resolves the link against the repository root:

Obviously, the preview won't work because the classes aren't present in any of the plugin repositories.

Maybe we can unlink the references and escape them, given the name already represents the FQN you can look up.

See https://github.com/jenkinsci/job-config-history-plugin/security/code-scanning/1 for a real world example.

[daniel-beck]

Thanks for letting me know. TBH this seems more like a bug in CodeQL/GitHub itself not recognizing that the class being referenced isn't in this repo?