Set up trusted types for lit.dev
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 230
- PR merge metrics
- No merged PRs in 30d
Description
A good idea generally for reducing the risk of XSS, but especially when we're handling GitHub tokens.
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 mapping the lit.dev TypeScript application and the places that handle GitHub tokens, then determine the intended Trusted Types coverage. Done should mean the agreed Trusted Types setup is applied and its XSS protections are verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- security, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100