Scorecard supply-chain security #66

	name: Scorecard supply-chain security
	on:
	branch_protection_rule:
	schedule:
	- cron: "22 6 * * 2"
	push:
	branches: [ "master" ]

	# Declare default permissions as read only.
	permissions: read-all

	jobs:
	analysis:
	name: Scorecard analysis
	runs-on: ubuntu-latest
	permissions:

	# Needed to upload the results to the code-scanning dashboard.
	security-events: write

	# Needed to publish the results and get a badge (see
	# `publish_results` below).
	id-token: write

	steps:
	- name: Harden Runner
	uses: step-security/harden-runner@5c7944e73c4c2a096b17a9cb74d65b6c2bbafbde # v2.9.1
	with:
	egress-policy: audit

	- name: "Checkout code"
	uses: actions/checkout@v4
	with:
	persist-credentials: false

	- name: "Run analysis"
	uses: ossf/[email protected]
	with:
	results_file: results.sarif
	results_format: sarif
	# (Optional) "write" PAT token. Uncomment the `repo_token` line below if:
	# - you want to enable the Branch-Protection check on a public repository, or
	# - you are installing Scorecard on a private repository
	# To create the PAT, follow the steps in https://github.com/ossf/scorecard-action?tab=readme-ov-file#authentication-with-fine-grained-pat-optional.
	# repo_token: ${{ secrets.SCORECARD_TOKEN }}
	publish_results: true

	- name: "Upload artifact"
	uses: actions/upload-artifact@v4
	with:
	name: SARIF file
	path: results.sarif
	retention-days: 5

	- name: "Upload to code-scanning dashboard"
	uses: github/codeql-action/upload-sarif@v3
	with:
	sarif_file: results.sarif

Provide feedback