chore: add support for OSSF scorecard reporting

[inigomarquinez]

Main Changes

This pipeline will proactively report the status of the project (every day and when a push is done to master branch) including critical fields (CI-Tests, Contributors, Dependency-Update-Tool, Webhooks) that are missing while running via OSSF cron jobs.

Context

Changes related

It's also possible that some repositories in your organization are already being automatically tracked by OpenSSF in this CSV file via weekly cronjob. One caveat: Automatically tracked projects do not include ossf/scorecard#3438 in their analysis (CI-Tests,Contributors,Dependency-Update-Tool,Webhooks).
Source: openssf-scorecard-monitor documentation

Team discussion related

• Ref: Implementing OSSF Scorecard expressjs/security-wg#2
• Report: https://kooltheba.github.io/openssf-scorecard-api-visualizer/#/projects/github.com/pillarjs/encodeurl/commit/5f2205efe622fc7972c4e45ed7cbe7f8d652c299

[blakeembrey]

Is there a reason we want to use the specific commit hashes instead of version numbers for every action?

[blakeembrey]

I'm a little worried about this, the package shouldn't need to be kept "up to date" re https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained.

[blakeembrey]

I found my answer here: https://github.com/ossf/scorecard/blob/d58bfb03aab496807d8489e09da9883928465f59/docs/checks.md#pinned-dependencies 😓

Seems like a GitHub Actions "lock file" would be a nice feature to simplify future updates.

[blakeembrey]

A heads up, but I'm already seeing this:

CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/

[inigomarquinez]

Sorry I didn't see your messages before @blakeembrey. Thanks for reviewing!

[Queenshg87]

Need review i believe..