Scorecard checks whether the project is fuzzed: listed in OSS-Fuzz, running ClusterFuzzLite, or defining language-level fuzz or property-based tests it recognises (Go native fuzzing and a limited set of property-based testing libraries for Haskell, JavaScript and TypeScript, Erlang, C# and F#). Other fuzzing set-ups may go undetected, so a low score is not conclusive.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.