-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Feature: add scorecard to your project #1298
Comments
/cc @isarkis @sethvargo |
@laurentsimon Thanks for bringing this up. I just ran |
I used this command to sign assets for the recent releases to comply with the recommendation of https://github.com/ossf/scorecard/blob/5758364c82f7fc72b256f9a8cfc89dc550d7dd66/docs/checks.md#signed-releases Ref Ref #1298
I used this command to sign assets for the recent releases to comply with the recommendation of https://github.com/ossf/scorecard/blob/5758364c82f7fc72b256f9a8cfc89dc550d7dd66/docs/checks.md#signed-releases Ref #1298
* Create SECURITY.md According to https://github.com/ossf/scorecard/blob/5758364c82f7fc72b256f9a8cfc89dc550d7dd66/docs/checks.md#security-policy Ref #1298 * Update SECURITY.md
* chore: Add signrel command for sigining arc release assets I used this command to sign assets for the recent releases to comply with the recommendation of https://github.com/ossf/scorecard/blob/5758364c82f7fc72b256f9a8cfc89dc550d7dd66/docs/checks.md#signed-releases Ref #1298 * Implement signrel subcommands for listing tags and signing assets, with docs
As a part of #1298, I'm going to use Go fuzzing which is availabls since Go 1.18.
As a part of #1298, I'm going to use Go fuzzing which is availabls since Go 1.18.
As a part of #1298, I'm going to use Go fuzzing which is availabls since Go 1.18. Co-authored-by: Callum Tait <15716903+toast-gear@users.noreply.github.com>
As a part of #1298, we add fuzzing based on Go test's fuzzing support to the test suite
As a part of #1298, we add fuzzing based on Go test's fuzzing support to the test suite
As a part of #1298, we add fuzzing based on Go test's fuzzing support to the test suite
We've managed to score 8.2 out of 10 now.
I think it's the best we can do today. |
I ran the OpenSSF's scorecard on this project and found that branch protection and code reviews are not enforced.
I chatted with @josepalafox and he suggested I create this issue to start a discussion.
Given the popularity of this project and its sensitivity (access to build pipeline, etc), it would be beneficial to install scorecard as suggested in the workflow hardening guideline.
/cc @nebuk89
The text was updated successfully, but these errors were encountered: