sjcl

Stanford Javascript Crypto Library

🌟 在 sjcl 的 README.md 中顯示即時使用量圖表，只需複製下面的代碼。

## Usage Trend
[![Usage Trend of sjcl](https://npm-compare.com/img/npm-trend/THREE_YEARS/sjcl.png)](https://npm-compare.com/sjcl#timeRange=THREE_YEARS)

🌟 在 sjcl 的 README.md 中顯示 GitHub stars 趨勢圖表，只需複製下面的代碼。

## GitHub Stars Trend
[![GitHub Stars Trend of sjcl](https://npm-compare.com/img/github-trend/sjcl.png)](https://npm-compare.com/sjcl)

套件	下載數	Stars	大小	Issues	發布時間	許可

sjcl	226,981	7,233	-	119	7 年前	(BSD-2-Clause OR GPL-2.0-only)

sjcl

Stanford Javascript Crypto Library

Security Advisories

12.02.2014: the current development version has a paranoia bug in the ecc module. The bug was introduced in commit ac0b3fe0 and might affect ecc key generation on platforms without a platform random number generator.

Security Contact

Security Mail: sjcl@ovt.me
OpenPGP-Key Fingerprint: 0D54 3E52 87B4 EC06 3FA9 0115 72ED A6C7 7AAF 48ED
Keyserver: pool.sks-keyservers.net

Upgrade Guide

1.0.3 -> 1.0.4

codecBase32 has been re-enabled with changes to conform to RFC 4648:

Padding with = is now applied to the output of fromBits. If you don't want that padding, you can disable it by calling fromBits with a second parameter of true or anything that evaluates as "truthy" in JS
The encoding alphabet for sjcl.codec.base32 now matches that specified by the RFC, rather than the extended hex alphabet.
The former extended hex alphabet is now available through sjcl.codec.base32hex (also matching the RFC). So if you encoded something with base32 before, you'll want to decode it with base32hex now.

Documentation

The documentation is available here