Register a verify endpoint with github secret scanning for DUATs
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
- add the verify token endpoint that checks for GITHUB-PUBLIC-KEY-IDENTIFIER and GITHUB-PUBLIC-KEY-SIGNATURE and then looks up an ApiToken with hash matching the provided token. Tombstone the token if found, possibly with a causal attribution of some sort
- register a regex with github
Contributor guide
No contributing guide indexed for this repository
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
Read the linked GitHub Secret Scanning Partner Program documentation first, then locate the ApiToken model and the endpoint entry points. Done means adding the verify-token endpoint and registering the requested regex, with matching tokens tombstoned as described in the checklist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100