chore: bump actions/setup-node from 6 to 7 - #73
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 6 to 7. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v6...v7) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
![bulwark-sc-ent[bot]](https://avatars.githubusercontent.com/b/255931?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary
| Severity | Count |
|---|---|
| High | 24 |
| Total | 24 |
Details
Grouped by audit rule and file. Line/column refer to the workflow or action YAML on the scanned branch.
template-injection — High
code injection via template expansion
File: .github/workflows/release.yaml
Fix guidance: https://docs.zizmor.sh/audits/#template-injection
Locations:
- Line 67–80 (cols 8–60) — this step
- Line 72 (cols 27–42) — expression
github.workflow— may expand into attacker-controllable code - Line 69 (cols 8–11) — this run block
unpinned-uses — High (10 similar finding(s))
unpinned action reference
File: .github/workflows/release.yaml
Fix guidance: https://docs.zizmor.sh/audits/#unpinned-uses
Locations:
- Line 19 (cols 14–33) — expression
actions/checkout@v7— action is not pinned to a hash (required by blanket policy) - Line 22 (cols 14–35) — expression
actions/setup-node@v7— action is not pinned to a hash (required by blanket policy) - Line 40 (cols 14–41) — expression
docker/setup-qemu-action@v4— action is not pinned to a hash (required by blanket policy) - Line 44 (cols 14–43) — expression
docker/setup-buildx-action@v4— action is not pinned to a hash (required by blanket policy) - Line 48 (cols 14–36) — expression
docker/login-action@v4— action is not pinned to a hash (required by blanket policy) - Line 57 (cols 14–41) — expression
docker/build-push-action@v7— action is not pinned to a hash (required by blanket policy) - Line 65 (cols 14–42) — expression
sigstore/cosign-installer@v3— action is not pinned to a hash (required by blanket policy) - Line 89 (cols 14–33) — expression
actions/checkout@v7— action is not pinned to a hash (required by blanket policy) - …and 2 more location(s) in this file.
cache-poisoning — High
runtime artifacts potentially vulnerable to a cache poisoning attack
File: .github/workflows/release.yaml
Fix guidance: https://docs.zizmor.sh/audits/#cache-poisoning
Locations:
- Line 57 (cols 8–41) — runtime artifacts usually published here
- Line 22 (cols 8–35) — enables caching by default
- Line 21–24 (cols 8–47) — this step
unpinned-uses — High (12 similar finding(s))
unpinned action reference
File: .github/workflows/test.yaml
Fix guidance: https://docs.zizmor.sh/audits/#unpinned-uses
Locations:
- Line 36 (cols 14–33) — expression
actions/checkout@v7— action is not pinned to a hash (required by blanket policy) - Line 38 (cols 14–33) — expression
actions/setup-go@v6— action is not pinned to a hash (required by blanket policy) - Line 53 (cols 14–33) — expression
actions/checkout@v7— action is not pinned to a hash (required by blanket policy) - Line 55 (cols 14–33) — expression
actions/setup-go@v6— action is not pinned to a hash (required by blanket policy) - Line 61 (cols 14–50) — expression
golangci/golangci-lint-action@v9.3.0— action is not pinned to a hash (required by blanket policy) - Line 74 (cols 14–33) — expression
actions/checkout@v7— action is not pinned to a hash (required by blanket policy) - Line 80 (cols 14–35) — expression
actions/setup-node@v7— action is not pinned to a hash (required by blanket policy) - Line 88 (cols 14–45) — expression
tj-actions/coverage-badge-go@v3— action is not pinned to a hash (required by blanket policy) - …and 4 more location(s) in this file.
Please review these findings before merging.
There was a problem hiding this comment.
Summary
| Severity | Count |
|---|---|
| High | 24 |
| Total | 24 |
Details
Grouped by audit rule and file. Line/column refer to the workflow or action YAML on the scanned branch.
template-injection — High
code injection via template expansion
File: .github/workflows/release.yaml
Fix guidance: https://docs.zizmor.sh/audits/#template-injection
Locations:
- Line 67–80 (cols 8–60) — this step
- Line 72 (cols 27–42) — expression
github.workflow— may expand into attacker-controllable code - Line 69 (cols 8–11) — this run block
unpinned-uses — High (10 similar finding(s))
unpinned action reference
File: .github/workflows/release.yaml
Fix guidance: https://docs.zizmor.sh/audits/#unpinned-uses
Locations:
- Line 19 (cols 14–33) — expression
actions/checkout@v7— action is not pinned to a hash (required by blanket policy) - Line 22 (cols 14–35) — expression
actions/setup-node@v7— action is not pinned to a hash (required by blanket policy) - Line 40 (cols 14–41) — expression
docker/setup-qemu-action@v4— action is not pinned to a hash (required by blanket policy) - Line 44 (cols 14–43) — expression
docker/setup-buildx-action@v4— action is not pinned to a hash (required by blanket policy) - Line 48 (cols 14–36) — expression
docker/login-action@v4— action is not pinned to a hash (required by blanket policy) - Line 57 (cols 14–41) — expression
docker/build-push-action@v7— action is not pinned to a hash (required by blanket policy) - Line 65 (cols 14–42) — expression
sigstore/cosign-installer@v3— action is not pinned to a hash (required by blanket policy) - Line 89 (cols 14–33) — expression
actions/checkout@v7— action is not pinned to a hash (required by blanket policy) - …and 2 more location(s) in this file.
cache-poisoning — High
runtime artifacts potentially vulnerable to a cache poisoning attack
File: .github/workflows/release.yaml
Fix guidance: https://docs.zizmor.sh/audits/#cache-poisoning
Locations:
- Line 57 (cols 8–41) — runtime artifacts usually published here
- Line 22 (cols 8–35) — enables caching by default
- Line 21–24 (cols 8–47) — this step
unpinned-uses — High (12 similar finding(s))
unpinned action reference
File: .github/workflows/test.yaml
Fix guidance: https://docs.zizmor.sh/audits/#unpinned-uses
Locations:
- Line 36 (cols 14–33) — expression
actions/checkout@v7— action is not pinned to a hash (required by blanket policy) - Line 38 (cols 14–33) — expression
actions/setup-go@v6— action is not pinned to a hash (required by blanket policy) - Line 53 (cols 14–33) — expression
actions/checkout@v7— action is not pinned to a hash (required by blanket policy) - Line 55 (cols 14–33) — expression
actions/setup-go@v6— action is not pinned to a hash (required by blanket policy) - Line 61 (cols 14–50) — expression
golangci/golangci-lint-action@v9.3.0— action is not pinned to a hash (required by blanket policy) - Line 74 (cols 14–33) — expression
actions/checkout@v7— action is not pinned to a hash (required by blanket policy) - Line 80 (cols 14–35) — expression
actions/setup-node@v7— action is not pinned to a hash (required by blanket policy) - Line 88 (cols 14–45) — expression
tj-actions/coverage-badge-go@v3— action is not pinned to a hash (required by blanket policy) - …and 4 more location(s) in this file.
Please review these findings before merging.
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
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.
Bumps actions/setup-node from 6 to 7.
Release notes
Sourced from actions/setup-node's releases.
... (truncated)
Commits
8207627Migrate to ESM and upgrade dependencies (#1574)04be95cAdd cache-primary-key and cache-matched-key as outputs (#1577)7c2c68ddocs: Update caching recommendations to mitigate cache poisoning risks (#1567)6a61c03Merge pull request #1569 from jasongin/update-actions-cache-5.1.030eb73bResolve high-severity audit issues4e1a87aUpdate dist360237fStrict equality4f8aac5Bump@actions/cacheto 5.1.0, log cache write deniedf4a67bbOnly usemirrorTokeningetManifestif it's provided (#1548)0355742Remove dummy NODE_AUTH_TOKEN export (#1558)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)