yahoo / yahoo/serialize-javascript

Use Function Objects for deserialization, instead of eval

Open
#158 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.9k
Forks
215
Avg merge
1d 12h
Merged PRs (30d)
2

Description

Use Function Objects for deserialization, instead of unsafe eval

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue only identifies deserialization and unsafe eval, with no file or test named. Start by locating the deserialization entry point in the repository and reviewing how serialized functions are currently evaluated. Done means deserialization no longer relies on unsafe eval while preserving the library's supported function handling.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
security
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.