advanced configuration for delayed/deferred secret availability
Open
Nobody has claimed this yet.
advanced configuration
enhancement
question
- Dominant language
- TypeScript
- Stars
- 141
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Still an open question whether this feature makes sense within this application but the ability to store a secret and get a link that only returns the value at some specified future date could be useful.
Related: https://github.com/osbytes/crypt.fyi/pull/11#issuecomment-2550466677
Contributor 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.
Research direction
The issue names no files, tests, or entry points. Start by reading the discussion on pull request #11 linked in the issue, then establish whether deferred secret availability belongs in this application and define its security model and acceptance criteria. Work is done only after the scope and behavior are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100