GitHub workflows already compliant with OpenSSF Scorecard Token-Permissions requirements #35
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
After comprehensive analysis of all GitHub workflow files in the repository, I've confirmed that the OpenTelemetry JS project is already fully compliant with OpenSSF Scorecard Token-Permissions requirements. No changes were needed.
Analysis Results
All 16 GitHub workflow files have proper minimum token permissions implemented:
✅ Root-Level Permissions Compliance
permissions: { contents: read }
(recommended minimal permissions)permissions: read-all
(sbom.yml - also acceptable)✅ Job-Level Permissions Compliance
Properly configured job-level permissions where needed:
benchmark.yml
:contents: write
(for pushing benchmark results to gh-pages)close-stale.yml
:issues: write
+pull-requests: write
(for closing stale issues/PRs)codeql-analysis.yml
:security-events: write
(for CodeQL analysis)docs.yaml
:contents: write
(for deploying documentation)ossf-scorecard.yml
:security-events: write
+id-token: write
(for OSSF scorecard)publish-to-npm.yml
:id-token: write
(for NPM provenance)sbom.yml
:contents: write
(for adding release artifacts)survey-on-merged-pr.yml
:contents: write
+pull-requests: write
(for PR surveys)✅ Security Best Practices Confirmed
secrets.GITHUB_TOKEN
vs custom tokensVerification Process
Created and ran a comprehensive verification script based on the OpenSSF Scorecard Token-Permissions check that analyzed all workflow files and confirmed 100% compliance:
The repository already follows security best practices and meets all OpenSSF Scorecard recommendations for GitHub Actions token permissions.
Fixes #34.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.