-
Notifications
You must be signed in to change notification settings - Fork 39
Improve OpenSSF Scorecard #289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We can probably replicate some of the things we did for OTEL Weaver to improve this score. |
jmacd
pushed a commit
that referenced
this issue
Mar 7, 2025
Regarding issue #289 Add CodeQL to the Go CI following usage in [Collector-Contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/.github/workflows/codeql-analysis.yml)
jmacd
pushed a commit
that referenced
this issue
Mar 17, 2025
Following inclusion of rust components in this repo, want to make sure all source code is accurately covered by CI. In addition, specify token permissions on each workflow to improve FOSSA score (#289).
jmacd
added a commit
that referenced
this issue
Apr 4, 2025
Per [Security Overview - Code Scanning Alerts](https://github.com/open-telemetry/otel-arrow/security/code-scanning) it is best practice to pin workflow action dependencies to specific commit hashes to avoid any unexpected and/or malicious behavior changes. These findings were recently surfaced by merge of #314, enabling ossf-scorecard scanning, which is happening across all OTel repositories. Should also help improve OSSF scorecard, see #289. Co-authored-by: Joshua MacDonald <[email protected]>
drewrelmas
added a commit
that referenced
this issue
May 8, 2025
Related to #289 I noticed an unexpected drop in [OpenSSF Scorecard results](https://scorecard.dev/viewer/?uri=github.com/open-telemetry/otel-arrow) - one of which is the Token-Permissions category. Details include the following warnings: > Warn: topLevel 'security-events' permission set to 'write': .github/workflows/go-ci.yml:5 Warn: no topLevel permission defined: .github/workflows/pipeline-perf-test.yml:1 This PR: * Restricts `security-events: write` to single job in `Go-CI` * Adds an explicit `contents: read` into `Pipeline Performance Tests` per best practice
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Improve
.
The text was updated successfully, but these errors were encountered: