zowe / zowe/api-layer

TSC: Integrate Scorecard Workflow

Open
#4,207 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Priority: Medium
Dominant language
Java
Stars
92
Forks
81
Avg merge
1d 9h
Merged PRs (30d)
46

Description

The TSC agreed that all of the squads needs to integrate the TSC Scorecard into the Workflows.

The details about the topic from Mark Ackert:

Per the recommendation in the linked PR, I created a modified scorecard workflow we can use to narrow the scan results to our preferred checks. The workflow is in the zowe-install-packaging repo here. A list of available checks are here, but the ID you need to supply to the workflow's SCORECARD_ENABLED_CHECKS differs slightly. I couldn't find a list of IDs, but you can look at the unfiltered results.sar if uploaded after each scorecard run to map a given check to it's ruleId.

There is also a question of efficient deployments of scorecards for large organizations which is in discussion https://github.com/ossf/scorecard/issues/4339. If the scorecard community comes up with a more elegant solution than duplicating a scorecard workflow across many repositories, we can look into adopting it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the reference workflow at .github/workflows/scorecards.yml in the zowe-install-packaging repository and the available Scorecard checks. Identify the api-layer workflows and the squads that need integration, then map enabled checks to their rule IDs using results.sar. Done means the agreed Scorecard workflow is integrated for the required squads with the selected checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.