gchq/CyberChef

Replace jsrsasign dependency

Open

#2325 opened on Apr 17, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (34,843 stars) (3,944 forks)batch import
help wantedinfra/meta

Description

Dependency "jsrsasign" will shortly go out of support:

https://github.com/kjur/jsrsasign/blob/master/README.md#end-of-support-announcement-for-jsrsasign

End of Support Announcement for jsrsasign On 14 April 2026, we announce end of support for jsrsasign.

Effective 3 Jun 2026, support is no longer provided for jsrsasign and all version of "npm" packages of jsrsasign is deprecated. Thank you very much for using jsrsasign since the release of its first version, 1.0, on June 3, 2010.

A new package should be found to replace this dependency.

Contributor guide

Tech stack
javascriptnodejs
Domain
securityfrontend
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptCryptographic primitives basicsnpm package management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate alternatives to jsrsasign, such as Node.js built in crypto module or node forge. Review the existing usage in the codebase (e.g., src/core/ or src/operations/) to understand required cryptographic functions. Check issue comments for suggestions. Once a replacement is chosen, update package.json and all imports.