Repository navigation
fix(security): resolve OpenSSF Scorecard token permissions, SAST, and pin dependency SHAs - #9
Merged
Conversation
…pendency SHAs - Enforce least privilege top-level permissions: read-all across all workflows - Pin all GitHub Action dependencies to full 40-character commit SHAs with inline version tags - Remove contents: write from dual-publish release workflow to eliminate elevated permissions - Replace unpinned npm install commands with pnpm install --frozen-lockfile - Add CodeQL SAST workflow (.github/workflows/codeql.yml) for automated static security analysis - Add osv-scanner.toml to document acknowledged dev vulnerabilities per OpenSSF guidelines
👋 Thanks for opening this Pull Request, @divyanshujethi!Thank you for contributing to MCP Builder Kit! ⚡ Here is what happens next:
|
|
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. |
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.
Summary of Changes
This PR remediates 26+ OpenSSF Scorecard Code Scanning security alerts across the repository:
1. Token-Permissions Hardening (Alerts #24, #25, #26)
elease.yml, scorecard.yml, est.yml, welcome-contributor.yml).
elease.yml:dual-publish, enforcing least privilege token access.
2. Pinned Dependencies by Commit SHA (Alerts #1 to #23)
pm ci || npm install in publishing workflows with strict pnpm install --frozen-lockfile (Alerts #20, #21, #22, #23).
3. Static Application Security Testing (SAST) (Alert #31)
4. Vulnerabilities Configuration (Alert #30)