apache / apache/infrastructure-actions
Track upstream verification/provenance requests blocking allowlist bumps
- Dominant language
- Python
- Stars
- 30
- Forks
- 83
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 79
Description
Several allowlist bumps are blocked on upstream actions adding verification or
provenance for artifacts they ship or download. Filing these individually works
- upstream has acted on them before - but there is nowhere to see which are
outstanding and what each one blocks.
## Open
| Upstream issue | Ask | Blocks |
| --- | --- | --- |
| ReactiveCircus/android-emulator-runner#485 | Verify the Android cmdline-tools zip after `tc.downloadTool`. No checksum today, and the `_latest` URL is republishable | #1100 - its last remaining finding |
| 1Password/load-secrets-action#186 | Add `actions/attest-build-provenance` or a `SHA256SUMS` release asset covering `dist/core_bg.wasm`, new in v5.0.0 and unattested | #1141 |
| 1Password/load-secrets-action#168 | Verify the `op` CLI download before extracting. Open since 2026-06-13, no response | carried over on every load-secrets-action bump |
## Resolved, as precedent that the ask lands
- runs-on/action#36 -> #37: maintainer added `actions/attest-build-provenance`
and started shipping `SHA256SUMS`; later bumps verify automatically.
- jdx/mise-action#547 -> #548: fixed same-day with signed-checksum
verification.
## How these should affect review
Pinning an action with a known finding is still strictly better than the
wildcard it replaces, so an open upstream request should not usually block a
bump on its own. The exception is a newly introduced opaque binary - the #1141
case - where no previously approved version carries the same exposure, so
accepting it would be a genuine regression rather than a carried-over warning.
---
Drafted-by: Claude Opus 5 (1M context) via Claude Code; reviewed by @potiuk before posting
Contributor guide
Research direction
Start with the Open table and the linked upstream issues ReactiveCircus/android-emulator-runner#485 and 1Password/load-secrets-action#186/#168. Confirm the status of each verification or provenance request and its affected allowlist bump; done means the outstanding blockers and relevant precedent are accurately tracked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100