Repository navigation
build(deps): bump anomalyco/opencode/github from 2.0.18 to 2.3.0 #1107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -29,7 +29,7 @@ | |
| persist-credentials: false | ||
|
|
||
| - name: Run opencode | ||
| uses: anomalyco/opencode/github@cd9a14a6b688d4021bee381dfd39d2cef9c0f862 # v2.0.18 | ||
| uses: anomalyco/opencode/github@a6b15d33daf6ab7d35569f6d711fdb630b9f04e7 # v2.3.0 | ||
|
Check failure on line 32 in .github/workflows/opencode.yml
|
||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🚨 This pin is broken: upstream deleted Technical details# Bump targets a tag with no action definition
## Affected sites
- `.github/workflows/opencode.yml:32` — `uses: anomalyco/opencode/github@a6b15d33daf6ab7d35569f6d711fdb630b9f04e7 # v2.3.0`
## Required outcome
- Do not merge: the pinned ref has no runnable action, so the step fails at resolution before `OPENCODE_API_KEY` is used.
- Retire/replace the workflow per upstream guidance, or repin to the last published action tag if maintainers accept depending on a removed action.
## Evidence
- `v2.3.0` resolves to `a6b15d33daf6ab7d35569f6d711fdb630b9f04e7`; `github/action.yml` returns 404 at that ref via the contents API, git tree API (12,511 entries, not truncated), and raw.githubusercontent.com.
- Commit `1743d1a24e23` "Remove the OpenCode GitHub Action (#59032)" (2026-10-25) deleted `github/` and both publish/release workflows. The v2.3.0 changelog records it under `v2.2.0 — 2026-10-27`: "The OpenCode GitHub Action is no longer published. Remove it from your workflows."
- The action's real tags are `github-v1.0.0` … `github-v1.2.28`; the last (`17b79f4e0c`, 2026-10-24) still contains `github/action.yml`. The current `v2.0.18` pin also still contains it, which is why the workflow works today.
- This workflow triggers only on `issue_comment` / `pull_request_review_comment`, so no PR check exercises it and CI will not catch the break. |
||
| env: | ||
| OPENCODE_API_KEY: ${{ secrets.OPENCODE_API_KEY }} | ||
| with: | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎟️ Issue Explanation
The workflow pins the action
anomalyco/opencode/githubto a full-length SHA commit (a6b15d33daf6ab7d35569f6d711fdb630b9f04e7), which is better than a mutable tag alone. However, the comment# v2.3.0is an unverified annotation — there is no cryptographic guarantee that this SHA actually corresponds to the official v2.3.0 release. More critically, the action runs with access tosecrets.OPENCODE_API_KEYand executes in a privileged CI context. If the SHA was obtained from a compromised registry, a typosquatted namespace (anomalycovs. the legitimate vendor), or an attacker-controlled fork, the action could exfiltrate secrets or tamper with the build pipeline. The previous pin (cd9a14a6b688d4021bee381dfd39d2cef9c0f862) was replaced without evidence of independent verification (e.g., SLSA provenance, sigstore/cosign signature). The repository context flags this workflow path (infra/ci/.github/workflows/) as high-risk (score 74) for secrets/pipeline exposure.🛠️ Actions
@secuarden-ai /fix- Generate remediation code for this issue@secuarden-ai /explain- Learn why this matters and potential impact@secuarden-ai /ignore [reason]- Dismiss this finding@secuarden-ai /review- Submit a reasoned assessment and request a rescan🔐 Secuarden Security Review • Finding:
SEC_ce8382e712df