Tests(fix[control]): Restore wrapper readiness #53

	# OpenSSF Scorecard: what this repository looks like to somebody deciding
	# whether to depend on it.
	#
	# The checks are about the project rather than the code — are actions pinned,
	# is the release process reproducible, is there a way to report a vulnerability.
	# Publishing the score means a regression in any of those is visible instead of
	# discovered by whoever was relying on it.
	name: scorecard

	on:
	branch_protection_rule:
	push:
	branches: [master]
	schedule:
	# Several checks read the state of the repository rather than the tree, so
	# they can change without a commit.
	- cron: '0 7 * * 1'
	workflow_dispatch:

	permissions: read-all

	concurrency:
	group: scorecard-${{ github.ref }}
	cancel-in-progress: true

	jobs:
	analysis:
	name: analysis
	runs-on: ubuntu-latest
	permissions:
	security-events: write
	id-token: write
	contents: read
	actions: read
	steps:
	- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
	with:
	persist-credentials: false

	- name: Run analysis
	uses: ossf/scorecard-action@2d1146689b8cda280b9bc96326124645441f03bc # v2.4.4
	with:
	results_file: results.sarif
	results_format: sarif
	# Publishing is what makes the badge and the public record work. It
	# sends the result, not the source.
	publish_results: true

	- uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
	with:
	name: scorecard-results
	path: results.sarif
	retention-days: 5

	- name: Upload to the security tab
	uses: github/codeql-action/upload-sarif@cdf488f595d80d6e07e03d4674febd5ab45fa938 # v4
	with:
	sarif_file: results.sarif

Navigation Menu