-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is this still maintained? #450
Comments
I have the same question. |
it is 2 years ago that it was last updated sooo. NO |
No new maintainer for the npm package: https://www.npmjs.com/package/crypto-js Best would be a team (GitHub "organization") creates a fork and takes over. |
Maybe you could try CryptoES. |
That's a great find, thanks very much! |
Besides CryptoES looks rougly 4 times faster for AES encrypt / decrypt on a development machine AMD Ryzen 7 5800H, Win 10 Node 18 LTS. The JSON is ~400 bytes length. // The encryption takes ~50 microseconds on CryptoES and ~200 microseconds on CryptoJS
const str = JSON.stringify(fixture);
const ciphertext = CryptoES.AES.encrypt(str, secret).toString();
// The decryption + JSON.parse takes ~40 microseconds on CryptoES and ~150 microseconds on CryptoJS
const bytes = CryptoES.AES.decrypt(ciphertext!, secret);
const str = bytes.toString(CryptoES.enc.Utf8);
const json = JSON.parse(str); |
Yes I've since moved to CryptoES, thanks @WhereJuly |
I`ve moved to CryptoES, but it is just as slow with 8MB base64 string encrypting |
No description provided.
The text was updated successfully, but these errors were encountered: