ci(053): supply-chain security workflows — CodeQL, Scorecard, dep-review, Trivy, SHA-pinning (WP-B1–B5)#501
Merged
Merged
Conversation
|
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:
For more information about GitHub Code Scanning, check out the documentation. |
Deploying mcpproxy-docs with
|
| Latest commit: |
deb39ee
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3e7b9c37.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://ci-053-supply-chain-security.mcpproxy-docs.pages.dev |
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 26272759907 --repo smart-mcp-proxy/mcpproxy-go
|
This was referenced May 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of spec 053 — OSS Repo Improvements (Track B, the highest-leverage track for a security product). One of ~3 PRs splitting the OSS-report backlog.
What's in here
.github/workflows/codeql.ymlgo+javascript-typescript(covers the Vuefrontend/+website/).build-mode: nonefor both — avoids flaky autobuild given this repo's-tags serverbuild. Push/PR tomain+ weekly schedule..github/workflows/scorecard.yml+ README badgeossf/scorecard-actionwithpublish_results: true,id-token: write; triggers onbranch_protection_rule+ schedule + push. SARIF → Security tab. Badge added to the README badge row..github/workflows/dependency-review.ymlactions/dependency-review-actiongating PRs,fail-on-severity: high, comment-on-failure. (PR-event only — the action requires it.)scanner-images.ymlghcr.io/.../scanner-*images (CRITICAL,HIGH; ignore-unfixed). Report-only (exit-code: 0) — scanner base images carry unfixable upstream CVEs; we want visibility, not a broken pipeline. SARIF → Security tab (distinct category per matrix leg). Gated to non-PR events since multi-platform builds can'tloadlocally.@vN→ 40-char commit SHA with# vX.Y.Zcomments. This is the highest-weight OpenSSF Scorecard item (Pinned-Dependencies). Dependabot (github-actions ecosystem, already configured) keeps them current. Local./.github/actions/*refs left as path refs.Verification
gh api(with annotated-tag dereferencing) and matched its# vX.Y.Zcomment — zero mismatches across all 18 distinct actions.grepconfirms no@vNexternal refs remain.Follow-ups (separate PRs / out of scope)
mainto require these checks) is a settings change — not in this PR.build-dockerjob inrelease.yml(if: false, "until server MVP") was intentionally not wired for Trivy since it never runs.🤖 Generated with Claude Code