gosuserpx8pro Thanks for providing the link to that image, because that enables responding to the issue in a substantive fashion.
Here is the documentation for that part (source). I have highlighted important text:
public final ComponentName getDeveloperVerificationServiceProvider ()
Return the component name of the developer verification service provider, for the purpose of interacting with the specific verifier in relation to extension parameters and response structure. Return null if the system verifier service provider is not available to the caller, or if there is no such provider specified by the system.
So any system that chooses not to participate can just return a null object reference.
In other words, AOSP contains a place where people managing each Android variant (e.g., Google, Samsung, GrapheneOS) can plug in developer verification checks, or not. I think anybody who finds the situation alarming is underinformed about how AOSP works.