ci: improve OpenSSF Scorecard security posture#230
Merged
Conversation
- Pin TrigenSoftware/simple-release-action@v1 by commit hash in release.yml (resolves 3 Scorecard PinnedDependenciesID alerts) - Add SLSA build provenance attestation via actions/attest-build-provenance@v4 in release-binaries.yml - Upload .sigstore.json bundles as release assets alongside binaries (addresses Scorecard Signed-Releases check, 0 → 8) - Add fuzz tests for ADR and project-config schema parsing layers (parseFrontmatter, parseAdr, AdrFrontmatterSchema, DomainNameSchema, DomainPrefixSchema, ProjectConfigSchema)
Deploying archgate-cli with
|
| Latest commit: |
f336052
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e1cf1e66.archgate-cli.pages.dev |
| Branch Preview URL: | https://fix-scorecard-env.archgate-cli.pages.dev |
rhuanbarreto
force-pushed
the
fix/scorecard-env
branch
from
ffdaf39 to
def7679
Compare
Adds a workflow_dispatch workflow that iterates over all existing releases, downloads each binary artifact, signs it with cosign (keyless OIDC via Sigstore), and uploads the .sigstore.json bundle as a release asset. Skips artifacts that already have a signature. This backfills the Scorecard Signed-Releases check for releases published before the attestation step was added to release-binaries.yml. Run once after merge, safe to re-run (idempotent).
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
1 participant
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
Addresses multiple OpenSSF Scorecard findings to improve the project's security score (currently 6.6/10).
CODEOWNERSTrigenSoftware/simple-release-action@v1by commit SHA inrelease.yml(3 occurrences). All actions across all workflows are now hash-pinned. ResolvesPinnedDependenciesIDalerts (8 → 10)actions/attest-build-provenance@v4torelease-binaries.yml. Generates SLSA build provenance attestations for each platform binary and uploads.sigstore.jsonbundles as release assets. AddressesSigned-Releasescheck (0 → 8). Users can verify withgh attestation verify <artifact> --repo archgate/cliparseAdr,parseFrontmatter,AdrFrontmatterSchema,DomainNameSchema,DomainPrefixSchema,ProjectConfigSchema) using hand-rolled generators (no new dependencies per ARCH-006)Expected Scorecard Impact
Test plan
bun run validatepasses (lint, typecheck, format, 688 tests, 22/22 ADR rules, build).sigstore.jsonfiles appear in GitHub Release assetsgh attestation verify <artifact> --repo archgate/cli