Key rotation without bloat
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- security
Research direction
The issue describes key rotation, historical attestations, time-bounded validity, and a claim-stack UX, but names no files, tests, or entry points. Clarify the intended data model, user flows, and acceptance criteria with maintainers before identifying an implementation location.
Written by the indexing model from the issue text.
Description
I'd like to be able to use keytrace for code signing purposes, where good hygene is often to have relatively short lived keys.
The old key attestations are still needed, so people can verify old code, code created with a key that was valid for that window.
I'd like some UX affordances to help manage this problem. I don't want people to be overwhelmed with old keys, but able to go back and look. I want them to be able to find keys that are meant for a certain time. I'd love to have declared what the valid use times are for keys.
I sort of imagine a claim stack, an ability for me to declare a sequence of keys where I can upsert a new one, roll off an old one. Ideally this allows >1 key at a time to be active, but declared as part of a group.
- Dominant language
- TypeScript
- Stars
- 86
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 orta/keytrace
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Similar issues
-
[测试] 等待仓库加载后再记录多仓库排序基线Possibly taken @myot233 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area:arcade p3-medium ready-for-agent testing type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fderuiter/deruiter.dev#2369 ·
Maintainers usually reply within 1 day
-
area:devenv origin:agent type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
overengineeringstudio/effect-utils#1949 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ccch1mneyyy/dsh-TUI#1631 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MiniMax-AI/minimax-code#507 ·
Maintainers usually reply within 1 day