chore: OSSF security baseline — CI, fuzzing, signed releases#10
Open
konih wants to merge 4 commits into
Open
Conversation
Add OpenSSF Scorecard, CodeQL, and preflight workflows; dependabot; README badges; golangci config; and CONTRIBUTING/justfile fixes. Roadmap left unchanged.
Add security policy, native Go fuzz tests with weekly CI, and a tag-triggered release workflow that builds binaries/packages and cosign-signs artifacts.
Run govulncheck on every push/PR, add just vulncheck, and bump the toolchain patch version so reachable stdlib CVEs are cleared.
Member
|
I really like the idea of automating the signing via the ci, however the current process works a bit different because of the npm packages we publish. I will have a look if we can just cherry-pick some sutff of this pr |
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
2 participants
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.
housekeeping PR — bumps OpenSSF Scorecard posture and makes the repo look maintained. no runtime behavior changes (except root help text).
what's in here
SECURITY.md— reporting, threat model, supply-chain verify instructionsscorecard.yaml— OpenSSF Scorecard (weekly + main)codeql.yaml— Go SASTpreflight.yaml— go mod tidy/verifyfuzz.yaml— native Go fuzz 30s (ParseSemver,TagFromReference)release.yaml— tag-triggered builds + cosign signed assetshack/release-assets.sh+hack/sign-release-assets.sh— binaries, nfpm packages, checksums, sigstore bundles.golangci.yml,just lint,just vulncheck, CONTRIBUTING fixesOpenSSF Scorecard checks this PR helps with
SECURITY.mdinternal/update,internal/ociref)sign-blob→*.sigstore.jsonon release assetsgo-test.ymlpermissions:per workflowstill repo-settings / follow-up
first release after merge: push a
v*.*.*tag (or workflow_dispatch with draft) to exerciserelease.yaml. Scorecard badge may take a run or two to update.test:
go test ./...,golangci-lint run ./...,just vulncheck,go test -run=^$ -fuzz=FuzzParseSemver -fuzztime=10s ./internal/update/...