libspectre reporting OSS-fuzz issues for Ghostscript
I think you might need to update libspectre's OSS-fuzz project file.
You currently have a public OSS-fuzz issue for libspectre that suggests that it found an "undefined behaviour" issue in Ghostscript, but as can be seen in Ghostscript's own project file it only tests address sanitizing and omits sanitizing for undefined behaviour.
So by libspectre using Ghostscript and using the default set of sanitizers by not specifying any at all, you are likely to see issues that will not be seen/fixed by Ghostscript. At some point in the future Ghostscript might enable undefined behaviour sanitizing in OSS-fuzz.
When you report OSS-fuzz bugs for Ghostscript, you cannot simply forward your bug report to Ghostscript like you did last time. It is better if you reproduce the issue OSS-fuzz using only Ghostscript without libspectre. That way it is clear that this is a Ghostscript bug and not something happening because of a bug in libspectre. My suggestion is that you put your own mailing list with at least one active maintainer on CC in the upstream Ghostscript bug report (perhaps Randy is only a contributor to libspectre and not one of the maintainers?). Since Randy haven't responded the upstream Ghostscript bug it is unfixed and will remain so until someone responds.
/ Sebastian