Encrypt session artifacts with repository-scoped broker keys and expose broker configuration
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
Start with the snapshot upload step in action.yml (around lines 705-720) and the broker input declared near lines 19-21, then trace how .github/workflows/review.yml forwards that input. Design the encryption and key-retrieval flow with maintainers first, since the broker protocol and key rotation are undecided. Done means a synthetic secret round-trips through encrypted upload and restore without appearing in the uploaded bytes, and a failed key fetch never falls back to plaintext.
Written by the indexing model from the issue text.
Description
#57 stores full Codex conversations and tool output as downloadable Actions artifacts. These may contain API keys or other credentials, and GitHub log masking does not sanitize artifact contents. No credential exposure has been confirmed.
Proposed fix
- Encrypt snapshots before upload and authenticate/decrypt them before extraction.
- For zero-configuration use, let the existing broker validate GitHub OIDC and return a repository-specific key. Keep the master key server-side and support an optional consumer-managed key.
- Forward a configurable
brokerinput through the reusable workflow. - Keep keys out of logs, artifacts and the agent environment. Never fall back to plaintext when key retrieval fails.
- Define key rotation and migration from existing plaintext snapshots, including their removal.
Verification
Test cross-event restore, repository isolation, wrong keys/tampering, upload failures, reruns and forked sessions. Failed operations must preserve the latest usable snapshot. A synthetic secret must round-trip without appearing in the uploaded bytes.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 39m
- Merged PRs (30d)
- 84
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from promplate/code-review
-
Stop retrying permanent GitHub API failures in retry.shPossibly taken @muspi-merol-review claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
promplate/code-review#113 · 1 comment ·
Maintainers usually reply within 1 day
-
Configure a git identity before the review agent runsPossibly taken @muspi-merol-review claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 1/100
promplate/code-review#112 · 1 comment ·
Maintainers usually reply within 1 day
-
Put the installed codex binary on PATH for review agentsPossibly taken @muspi-merol-review claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 35/100
promplate/code-review#111 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Document Issues write as required for reactions, not just issuesPossibly taken @muspi-merol-review claimed this today. Opendocumentation
Difficulty 1/5 Under an hour Newbie friendliness 25/100
promplate/code-review#100 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
wait-ci.sh never receives the token it excludes sibling runs withPossibly taken @muspi-merol-review claimed this today. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
promplate/code-review#98 · 1 comment ·
Maintainers usually reply within 1 day
All issues in promplate/code-review
Similar issues
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
サムネイルの Storage のバケット(`thumbnails`)に、大きさの上限(1 MiB)と許可する種類(JPEG、PNG、WebP)を設定するPossibly taken @ykzts claimed this today. Opentech: supabase
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
inabagumi/shinju-date#7147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elecnix/your-attention#129 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
umami-software/umami#4780 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
celo-org/social-connect#487 ·
Maintainers usually reply within 1 day