Remove unnecessary JavaScript `eval` for non-`unsafe-eval` environments
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 875
- Forks
- 68
- Avg merge
- 9d 5h
- Merged PRs (30d)
- 1
Description
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
Start with the linked external issue and comment, then trace where JavaScript eval is used in ruby.wasm. Confirm which non-unsafe-eval environments are affected; done means the unnecessary eval path is removed while the relevant environments continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, ruby, wasm
- Domain
- security, web-dev
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100