chore: apply security best practices and onboard stepsecurity#131
Merged
chore: apply security best practices and onboard stepsecurity#131
Conversation
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF ScorecardScorecard details
Scanned Files
|
akshay29595
approved these changes
Nov 6, 2025
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.
This pull request updates the GitHub Actions workflows to improve security and reliability. The main changes include hardening the CI runners, pinning action versions to specific commit SHAs, and updating permissions for certain jobs.
Security hardening and workflow improvements:
step-security/harden-runneraction to all workflows (commit-lint.yml,npm-publish.yml,pull_request_checks.yml), blocking all network egress except for globally allowed endpoints. [1] [2] [3]actions/checkoutandactions/setup-nodewith specific commit SHAs to prevent supply chain attacks. [1] [2] [3]aws-actions/configure-aws-credentials,aws-actions/aws-secretsmanager-get-secrets) to specific commit SHAs innpm-publish.yml.Permissions and access control:
permissionsblocks to restrict and explicitly define required permissions for jobs, including grantingid-token: writewhere needed for OIDC authentication. [1] [2]