Conversation
See actions/checkout#485 See https://docs.zizmor.sh/audits/#artipacked From the docs: > By default, using `actions/checkout` causes a credential to be persisted on > disk. Versions below v6.0.0 store the credential directly in the checked-out > repo's `.git/config`, while v6.0.0 and later store it under `$RUNNER_TEMP`. > Subsequent steps may accidentally publicly persist the credential, e.g. by > including it in a publicly accessible artifact via actions/upload-artifact. > However, even without this, persisting the credential on disk is non-ideal > unless actually needed. > Starting with zizmor v1.17.0, this audit produces lower-severity findings > when v6.0.0 or higher of actions/checkout is used. This reflects a change > in v6.0.0's credential persistence behavior towards a more misuse-resistant > location. > See orgs/community#179107 for additional information.
Resolves the following: ``` error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack --> ./.github/workflows/build-and-release.yml:27:9 | 2 | / on: 3 | | push: 4 | | tags: 5 | | - 'v*' | |____________- generally used when publishing artifacts generated at runtime ... 27 | uses: actions/setup-go@4a36011 # v6.4.0 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default | = note: audit confidence → Low = note: this finding has an auto-fix ```
Per https://github.com/actions/attest-build-provenance/blob/v4.1.0/README.md **As of version 4, `actions/attest-build-provenance` is simply a wrapper on top of [`actions/attest`][7].** Existing applications may continue to use the `attest-build-provenance` action, but new implementations should use `actions/attest` instead. Please see the [`actions/attest`][7] repository for usage information. Documentation for previous versions of this action can be found [here](https://github.com/actions/attest-build-provenance/blob/v3.2.0/README.md). [7]: https://github.com/actions/attest
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
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.
This PR adds a job to run
zizmoragainst all of the GitHub Actions workflows.It surfaced a good handful of issues! So I fixed those up as well.