Add last used timestamp for personal access tokens
Open
Nobody has claimed this yet.
aspect: security
component: dashboard
feature: public-api
meta: never-stale
needs visual design
type: improvement
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
Following the work in https://github.com/gitpod-io/gitpod/issues/14280 and the relevant RFC (internal), the personal access tokens currently do not store or surface the last used timestamp which is usually a best practice for access tokens.
See also relevant discussion (internal). Cc @easyCZ
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
No files, tests, or entry points are named. Start by reviewing issue 14280 and the linked RFC, then trace where personal access tokens are stored, used, and surfaced; done means recording and exposing a last-used timestamp consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, backend-api-design, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100