You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+1-16
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ It also automatically builds and tests your code using [GitHub Actions](https://
25
25
* Static code analysis using [CodeQL](https://codeql.github.com/) and [Go Report Card](https://goreportcard.com/).
26
26
* Coverage analysis using the [go-test-coverage action](https://github.com/vladopajic/go-test-coverage).
27
27
* Security analysis using [OpenSSF](https://securityscorecards.dev).
28
-
* Signed binary artifacts using [Sigstore](https://www.sigstore.dev/)'s [cosign](https://github.com/sigstore/cosign).
28
+
* Signed binary artifacts using [artifact attestations](https://docs.github.com/en/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
29
29
30
30
## How to use
31
31
@@ -115,18 +115,3 @@ Issues are welcome.
115
115
116
116
PRs are also welcome, but keep in mind that this is a very opinionated template, so not all changes will be accepted.
117
117
PRs also need to ensure that test coverage remains high, and best practices are followed.
118
-
119
-
## How to verify binary signatures
120
-
121
-
1. Download the three `checksums` files. They should end in `_checksums.txt`, `_checksums.txt.pem`, and `_checksums.txt.sig`.
122
-
2. Verify using [cosign](https://github.com/sigstore/cosign). For example:
0 commit comments