Migrate from ujson to orjson

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend, cloud

Research direction

Start by locating where ujson is imported and used in the Lambda layer, then compare those call sites with orjson's documented behavior. The migration is done when the project no longer depends on ujson, uses orjson in its existing serialization paths, and the relevant tests or checks still pass.

Written by the indexing model from the issue text.

Description

ujson is currently not supported, and is in maintenance mode

[!WARNING] UltraJSON's architecture is fundamentally ill-suited to making changes without risk of introducing new security vulnerabilities. As a result, this library has been put into a maintenance-only mode. Support for new Python versions will be added and critical bugs and security issues will still be fixed but all other changes will be rejected. Users are encouraged to migrate to orjson which is both much faster and less likely to introduce a surprise buffer overflow vulnerability in the future.
https://pypi.org/project/ujson/

'orjson' -> https://pypi.org/project/orjson/

hopefully it's a drop-in replacement

Dominant language
Python
Stars
102
Forks
52
No merged PRs in 30d

Contributor guide

Open the contributing guide

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.

More from DataDog/datadog-lambda-python

All issues in DataDog/datadog-lambda-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.