Skip to content

ci: add a security policy, Scorecard and CodeQL - #17

Closed
jd wants to merge 1 commit into
mainfrom
devs/jd/jd/followon-174/add-security-policy-scorecard-codeql--d7bb2a36
Closed

jd wants to merge 1 commit into
mainfrom
devs/jd/jd/followon-174/add-security-policy-scorecard-codeql--d7bb2a36

Conversation

@jd

@jd jd commented Oct 21, 2026

Copy link
Copy Markdown
Member

This repository ships a GitHub Action that runs in other people's CI, and
it has had no security policy and no code scanning.

SECURITY.md sends vulnerability reports to Mergify's HackerOne program,
other security questions to security@mergify.com, and links the
disclosure policy, the same as the mergify-cli repository. It also says
how fixes reach users: a new vX.Y.Z release, with v1 moved to it.

.github/workflows/scorecard.yaml runs OpenSSF Scorecard on pushes to
main, weekly and on branch protection changes, publishes the result to
the Scorecard API and uploads the SARIF to code scanning. The job runs
on ubuntu-latest rather than ubuntu-26.04: the API only accepts
results from a workflow that follows its restrictions, and its list of
runner labels does not include 26.04 yet.

.github/workflows/codeql.yaml runs CodeQL with the actions language
on pull requests, on main and weekly. That language covers both the
workflows and action.yml, including the composite action's shell step,
which is where an injection would reach users.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

This repository ships a GitHub Action that runs in other people's CI, and
it has had no security policy and no code scanning.

SECURITY.md sends vulnerability reports to Mergify's HackerOne program,
other security questions to security@mergify.com, and links the
disclosure policy, the same as the mergify-cli repository. It also says
how fixes reach users: a new vX.Y.Z release, with `v1` moved to it.

`.github/workflows/scorecard.yaml` runs OpenSSF Scorecard on pushes to
main, weekly and on branch protection changes, publishes the result to
the Scorecard API and uploads the SARIF to code scanning. The job runs
on `ubuntu-latest` rather than `ubuntu-26.04`: the API only accepts
results from a workflow that follows its restrictions, and its list of
runner labels does not include 26.04 yet.

`.github/workflows/codeql.yaml` runs CodeQL with the `actions` language
on pull requests, on main and weekly. That language covers both the
workflows and action.yml, including the composite action's shell step,
which is where an injection would reach users.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Change-Id: Id7bb2a36ac14cd6b9359d2c744fa1baf1a583682
@mergify
mergify Bot had a problem deploying to Mergify Merge Protections October 21, 2026 01:23 Failure
@mergify

mergify Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Merge Protections

🔴 2 of 6 protections blocking · waiting on 👀 reviews

Protection Waiting on
🔴 👀 Review Requirements 👀 reviews
🔴 🔎 Reviews 👀 reviews
🟢 🤖 Continuous Integration —
🟢 Enforce conventional commit —
🟢 📕 PR description —
🟢 🚦 Auto-queue —

🔴 👀 Review Requirements

Waiting for

  • #approved-reviews-by>=1
This rule is failing.
  • any of:
    • #approved-reviews-by>=1
    • author = dependabot[bot]
    • author = mergify-ci-bot
    • author = renovate[bot]

🔴 🔎 Reviews

Waiting for

  • #review-requested = 0
This rule is failing.
  • #review-requested = 0
  • #changes-requested-reviews-by = 0
  • #review-threads-unresolved = 0

Show 4 satisfied protections

🟢 🤖 Continuous Integration

  • all of:
    • check-success=all-greens

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@mergify
mergify Bot requested a review from a team October 21, 2026 01:24
@jd

jd commented Oct 21, 2026

Copy link
Copy Markdown
Member Author

Closing: we're dropping the supply-chain hardening effort for now, no bandwidth for it.

@jd jd closed this Oct 21, 2026

This branch had an error being deployed

1 failed deployment
Mergify Merge Protections — b2059606 Deployed Oct 21, 2026 by mergify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants