🐛 Skip CODEOWNERS file in contributors check if there is a parsing error

[juanis2112]

What kind of change does this PR introduce?

Bug Fix

• PR title follows the guidelines defined in our pull request documentation

What is the current behavior?

When running scorecard on the repo: https://github.com/IBM/vllm I run into the following error:

Error: check runtime error: Contributors: internal error: Client.Repositories.ListContributors: error during contributorsHandler.setup: error during ParseFile: line 55: unexpected character '^' at position 17
2025/08/25 12:22:59 error during command execution: check runtime error: Contributors: internal error: Client.Repositories.ListContributors: error during contributorsHandler.setup: error during ParseFile: line 55: unexpected character '^' at position 17
exit status 1

What is the new behavior (if this is a feature change)?**

The Codeowners file is skipped if there are parsing errors found so now running scorecard on the repo https://github.com/IBM/vllm shows a score instead of error.

• Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes

Fixes #4768

Special notes for your reviewer

I plan to open an issue in the hmarr/codeowners
package, as I believe they could benefit from supporting the ^ character in their parsing patterns. Regardless, it’s better for Scorecards to skip the CODEOWNERS file if a parsing error occurs and still produce a score, rather than invalidating the entire check. This change addresses that need.

We could optionally print a message to inform the user that a CODEOWNERS file was skipped, happy to add that if it’s useful.

Does this PR introduce a user-facing change?

For user-facing changes, please add a concise, human-readable release note to
the release-note

(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

NONE

[spencerschrock]

I plan to open an issue in the hmarr/codeowners
package, as I believe they could benefit from supporting the ^ character in their parsing patterns

Is that a valid CODEOWNERS character? I noticed the upstream VLLM fixed their codeowners, so I suspect it was a temporary mistake.

vllm-project/vllm@cf278ff

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 69.59%. Comparing base (353ed60) to head (53ed294).
⚠️ Report is 282 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4851      +/-   ##
==========================================
+ Coverage   66.80%   69.59%   +2.78%     
==========================================
  Files         230      251      +21     
  Lines       16602    15657     -945     
==========================================
- Hits        11091    10896     -195     
+ Misses       4808     3891     -917     
- Partials      703      870     +167     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[spencerschrock]

Looks great thanks