sjcl

Stanford Javascript Crypto Library

🌟 Muestra el gráfico de uso en tiempo real en el README.md de sjcl, simplemente copia el código a continuación.

## 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)

🌟 Muestra el gráfico de tendencia de GitHub Stars en el README.md de sjcl, simplemente copia el código a continuación.

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

Paquete	Descargas	Stars	Tamaño	Issues	Publicación	Licencia

sjcl	226,981	7,233	-	119	hace 7 años	(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