Encrypt session artifacts with repository-scoped broker keys and expose broker configuration

Open
#66 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions
Domain
ci-cd, security

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 broker input 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.

Current upload · Broker input · Reusable workflow

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from promplate/code-review

All issues in promplate/code-review

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.