Skip to content

build(deps): bump ossf/scorecard-action from 99c09fe975337306107572b4fdf4db224cf8e2f2 to 4eaacf0543bb3f2c246792bd56e8cdeffafb205a in /.github/workflows#170

Merged
fr4nc1sc0-r4m0n merged 2 commits into
mainfrom
dependabot/github_actions/dot-github/workflows/ossf/scorecard-action-4eaacf0543bb3f2c246792bd56e8cdeffafb205a
Mar 31, 2026
Merged

build(deps): bump ossf/scorecard-action from 99c09fe975337306107572b4fdf4db224cf8e2f2 to 4eaacf0543bb3f2c246792bd56e8cdeffafb205a in /.github/workflows#170
fr4nc1sc0-r4m0n merged 2 commits into
mainfrom
dependabot/github_actions/dot-github/workflows/ossf/scorecard-action-4eaacf0543bb3f2c246792bd56e8cdeffafb205a

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Mar 29, 2026

Bumps ossf/scorecard-action from 99c09fe975337306107572b4fdf4db224cf8e2f2 to 4eaacf0543bb3f2c246792bd56e8cdeffafb205a.

Changelog

Sourced from ossf/scorecard-action's changelog.

Releasing the scorecard GitHub Action

This is a draft document to describe the release process for the scorecard GitHub Action.

(If there are improvements you'd like to see, please comment on the tracking issue or issue a pull request to discuss.)

Tracking

As the first task, a Release Manager should open a tracking issue for the release.

We don't currently have a template for releasing, but the following issue is a good example to draw inspiration from.

We're not striving for perfection with the template, but the tracking issue will serve as a reference point to aggregate feedback, so try your best to be as descriptive as possible.

Preparing the release

This section covers changes that need to be issued as a pull request and should be merged before releasing the scorecard GitHub Action.

Validate the Action

Manually run the workflow scorecards.yml and verify that the run succeeds.

Update the scorecard-action version

NOTE: we have a chicken-and-egg problem where the commit to be used for the release needs to have the image tag that only gets created after the commit is pushed. We workaround that by pre-selecting and referencing the image tag instead of the SHA which isn't ideal but workable.

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [ossf/scorecard-action](https://github.com/ossf/scorecard-action) from 99c09fe975337306107572b4fdf4db224cf8e2f2 to 4eaacf0543bb3f2c246792bd56e8cdeffafb205a.
- [Release notes](https://github.com/ossf/scorecard-action/releases)
- [Changelog](https://github.com/ossf/scorecard-action/blob/main/RELEASE.md)
- [Commits](ossf/scorecard-action@99c09fe...4eaacf0)

---
updated-dependencies:
- dependency-name: ossf/scorecard-action
  dependency-version: 4eaacf0543bb3f2c246792bd56e8cdeffafb205a
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Mar 29, 2026
@dependabot dependabot Bot requested a review from a team as a code owner March 29, 2026 22:05
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Mar 29, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Dependency Update Analysis

Summary: This PR updates one GitHub Action (ossf/scorecard-action) to a newer SHA for v2.4.3; compatibility risk is low for this repo’s current usage, but I did not apply oblt-aw/ai/merge-ready because upstream release notes include security-relevant internal changes (no CVE/GHSA IDs, but security-fix/hardening entries).

Dependency 1: ossf/scorecard-action 99c09fe975337306107572b4fdf4db224cf8e2f24eaacf0543bb3f2c246792bd56e8cdeffafb205a

Ecosystem: GitHub Actions

Check Result
Breaking changes ✅ None found affecting this repo’s usage
Testable in PR ✅ Yes — workflow is triggered by pull_request (.github/workflows/ci.yml:5-9)
Commit verified ✅ Yes (4eaacf... is GitHub-verified)
Pin format ✅ SHA-pinned
Changelog highlights (vOLD → vNEW)
  • Action bump is in .github/workflows/ci.yml:100.
  • Upstream scorecard-action v2.4.3 release bumps embedded Scorecard engine to v5.3.0 and includes docs/maintenance updates.
  • No explicit CVE IDs or GHSA advisories were listed in v2.4.3 release notes.
  • Upstream scorecard v5.3.0 notes include security-relevant hardening/behavior updates (for example symlink traversal handling, webhook payload size limiting, and additional dangerous-workflow detections).
Usage in this repository
  • Only usage found: .github/workflows/ci.yml:100.
  • Inputs used:
    • results_file: scorecard-results.sarif (.github/workflows/ci.yml:102)
    • results_format: sarif (.github/workflows/ci.yml:103)
    • publish_results: false (.github/workflows/ci.yml:104)
  • Output path is consumed by github/codeql-action/upload-sarif (.github/workflows/ci.yml:106-109).
Compatibility assessment
  • The workflow’s consumed interface (action invocation + SARIF output upload) is unchanged; no required new inputs were identified.
  • Commit provenance checks pass for the new SHA and it maps to tag v2.4.3.
  • CVE-focused assessment:
    • Identified vulnerability entries: No CVE/GHSA identifiers in scorecard-action v2.4.3 release notes.
    • Internal security-impacting changes: Upstream engine changes emphasize safer parsing/analysis behavior and stronger detection logic.
    • Risk impact for this repo: Overall risk preserved to slightly reduced for security posture; operationally, the main risk is potential analysis-result drift (more/changed findings), not runtime compromise.
    • Potential regressions / attack surface: No new permission scopes in this workflow beyond existing job permissions (actions: read, contents: read, security-events: write, id-token: write in .github/workflows/ci.yml:88-92). Main regression vector is CI noise/false positives from updated checks.

Labels Applied

No labels applied.

Note

🔒 Integrity filtering filtered 1 item

Integrity filtering activated and filtered the following item during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.


What is this? | From workflow: Observability Agentic Workflow Entrypoint

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

…ws/ossf/scorecard-action-4eaacf0543bb3f2c246792bd56e8cdeffafb205a
Comment thread .github/workflows/ci.yml

- name: Run Scorecard analysis
uses: ossf/scorecard-action@99c09fe975337306107572b4fdf4db224cf8e2f2 # v2.4.3
uses: ossf/scorecard-action@4eaacf0543bb3f2c246792bd56e8cdeffafb205a # v2.4.3
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot update the version in the comment as well

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comment is already correct — both SHAs refer to the same v2.4.3 release. Dependabot pinned to the annotated tag object SHA (99c09fe…) before, and is now using the underlying commit SHA (4eaacf0…) that the tag points to. No version change occurred, so the # v2.4.3 comment remains accurate.

@github-actions
Copy link
Copy Markdown
Contributor

Dependency Update Analysis

Summary: This PR updates ossf/scorecard-action in CI from 99c09fe975337306107572b4fdf4db224cf8e2f2 to 4eaacf0543bb3f2c246792bd56e8cdeffafb205a (commented as v2.4.3); overall risk is low-to-moderate due mostly to scanner-behavior changes rather than runtime app impact.

ossf/scorecard-action 99c09fe...4eaacf0...

Ecosystem: GitHub Actions

Check Result
Breaking changes ✅ None found in this repo usage
Testable in PR ✅ Yes — workflow triggers on pull_request to main (.github/workflows/ci.yml lines 5-9)
Commit verified ⚠️ Partially verified — v2.4.3 annotated tag is cryptographically verified and points to commit 4eaacf...; direct commit-signature status was not available from the MCP commit response
Pin format ✅ SHA-pinned
Changelog highlights (`v2.4.2` → `v2.4.3`)
  • scorecard-action v2.4.3 bumps underlying ossf/scorecard engine to v5.3.0.
  • Notable security-relevant engine changes in v5.3.0 release notes include:
    • Symlink handling hardening (skip dangling symlinks, detect symlink path traversal in local file mode).
    • Dangerous workflow detections expanded (discussion title/body, blocked user fields).
    • Pinned-dependency detection improvements and bug fixes (unpinned reusable workflows, docker pin detection, parsing fixes).
    • Payload-size limiting in webhook paths (1024 bytes), reducing abuse surface.
  • No explicit CVE IDs or GHSA advisories were listed in the action v2.4.3 release body.
Usage in this repository
  • Found at .github/workflows/ci.yml line 100:
    • uses: ossf/scorecard-action@4eaacf0543bb3f2c246792bd56e8cdeffafb205a # v2.4.3
  • Job context (scorecard job):
    • Inputs: results_file, results_format: sarif, publish_results: false.
    • Permissions: actions: read, contents: read, security-events: write, id-token: write.
    • Output consumed by github/codeql-action/upload-sarif.
  • Trigger context: workflow runs on PR events (opened, synchronize, reopened) targeting main.
Compatibility + CVE-focused assessment
  • Breaking/API compatibility: No action input changes were identified that affect current usage (results_file, results_format, publish_results).
  • Security exposure impact for this repo:
    • Changes are primarily in static-analysis logic and detection fidelity, not in this repository’s application/runtime path.
    • Improved detection logic likely reduces missed-findings risk (especially workflow/pinning patterns).
    • No new privileged scopes were introduced in this repo’s workflow by this PR.
  • Potential regressions / new attack surface:
    • Main risk is CI signal behavior drift (new or noisier findings) due upgraded detection heuristics.
    • Operationally low blast radius: Scorecard runs in CI and publishes SARIF; no direct production execution path.
  • Overall risk level: low-to-moderate.

Labels Applied

No labels applied.

Reason: based on available MCP data, commit verification was only partially confirmable (verified signed tag -> target commit), while direct commit verification status was not exposed in the commit response. I therefore did not auto-apply oblt-aw/ai/merge-ready.

Note

🔒 Integrity filtering filtered 1 item

Integrity filtering activated and filtered the following item during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.


What is this? | From workflow: Observability Agentic Workflow Entrypoint

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 31, 2026

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • https://api.github.com/repos/ossf/scorecard-action/git/commits/4eaacf0543bb3f2c246792bd56e8cdeffafb205a
    • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (http block)

If you need me to access, download, or install something from one of these locations, you can either:

Copy link
Copy Markdown
Contributor

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n merged commit c30da9e into main Mar 31, 2026
58 checks passed
@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n deleted the dependabot/github_actions/dot-github/workflows/ossf/scorecard-action-4eaacf0543bb3f2c246792bd56e8cdeffafb205a branch March 31, 2026 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants