Skip to content

Add Scorecard workflow for supply-chain security analysis #122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mitchelsellers merged 1 commit into from
Mar 19, 2026
+60 −0
Merged

Add Scorecard workflow for supply-chain security analysis #122

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
60 changes: 60 additions & 0 deletions .github/workflows/ossf-scorecard.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
name: "Scorecard supply-chain security"
on:
# For Branch-Protection check. Only the default branch is supported. See
# https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection
branch_protection_rule:

# To guarantee Maintained check is occasionally updated. See
# https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained
schedule:
- cron: "45 10 * * 0"
push:
branches: ["develop"]

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

Check warning on line 15 in .github/workflows/ossf-scorecard.yml

View check run for this annotation

SonarQubeCloud / SonarCloud Code Analysis

Replace "read-all" with specific permissions (e.g., "contents: read"). 


See more on https://sonarcloud.io/project/issues?id=IowaComputerGurus_netcore.utilities.spreadsheet&issues=AZ0GTp22LxbCdAtIp8N8&open=AZ0GTp22LxbCdAtIp8N8&pullRequest=122

Check notice

Code scanning / SonarCloud

Read-all and Write-all permissions should not be used Low

Replace "read-all" with specific permissions (e.g., "contents: read"). See more on SonarQube Cloud

jobs:
analysis:
name: "Scorecard analysis"
runs-on: "ubuntu-latest"
if: ${{ github.event.repository.default_branch == github.ref_name || github.event_name == 'pull_request' }}
permissions:
# Needed to upload the results to code-scanning dashboard.
security-events: "write"
# Needed to publish results and get a badge (see publish_results below).
id-token: "write"
Comment on lines +22 to +26

steps:
- name: "Checkout code"
uses: "actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd" # v6.0.2
with:
persist-credentials: false

- name: "Run analysis"
uses: "ossf/scorecard-action@4eaacf0543bb3f2c246792bd56e8cdeffafb205a" # v2.4.3
with:
results_file: results.sarif
results_format: sarif

# Public repositories:
# - Publish results to OpenSSF REST API for easy access by consumers
# - Allows the repository to include the Scorecard badge.
# - See https://github.com/ossf/scorecard-action#publishing-results.
publish_results: true

# Upload the results as artifacts (optional). Commenting out will disable uploads of run results in SARIF
# format to the repository Actions tab.
- name: "Upload artifact"
uses: "actions/upload-artifact@bbbca2ddaa5d8feaa63e36b76fdaad77386f024f" # v7.0.0
with:
name: "SARIF file"
path: "results.sarif"
retention-days: 5

# Upload the results to GitHub's code scanning dashboard (optional).
# Commenting out will disable upload of results to your repo's Code Scanning dashboard
- name: "Upload to code-scanning"
uses: "github/codeql-action/upload-sarif@b1bff81932f5cdfc8695c7752dcee935dcd061c8" # v4.33.0
with:
sarif_file: "results.sarif"
Loading