The score card should indicate when checks don't support a particular language/ecosystem

The scorecard can be populated for any open source project without any work or interaction from maintainers.

Maintainers must be provided with a mechanism to correct any automated scorecard findings they feel were made in error, provide "hints" for anything we can't detect automatically, and even dispute the applicability of a given scorecard finding for that repository.

There are some checks, like fuzzing, that are very specific to particular languages.

I think any score card should make clear when a particular check doesn't natively support a language or ecosystem.

As someone who is a consumer, and a maintainer, it would be good to know that a project didn't really score zero on something. It's just that the check doesn't support that language/ecosystem vs the maintainer has gone to the effort of somehow flagging that they do something the automated checks can't pick up.

Review the existing scorecard check implementations, starting with language-specific checks such as fuzzing, and trace how their results are represented in the scorecard output. Define how an unsupported language or ecosystem should be distinguished from a failed check, then verify that the output clearly communicates that distinction without changing the meaning of genuine zero scores.