Is sjcl-codec-utf8-string safe to use?

sjcl-codec-utf8-string has no known vulnerabilities on the latest version (1.0.0). DepScope rates its health at 42/100 (high risk).

What is the latest version of sjcl-codec-utf8-string?

The latest version of sjcl-codec-utf8-string is 1.0.0, released 2015-12-31.

Does sjcl-codec-utf8-string have known vulnerabilities?

No known vulnerabilities on the latest version of sjcl-codec-utf8-string.

Is sjcl-codec-utf8-string deprecated?

No, sjcl-codec-utf8-string is actively maintained. Latest release: 1.0.0 (2015-12-31).

What are alternatives to sjcl-codec-utf8-string?

Popular alternatives to sjcl-codec-utf8-string in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does sjcl-codec-utf8-string use?

sjcl-codec-utf8-string is licensed under BSD or GPL 2.0.

sjcl-codec-utf8-string

npmv1.0.0

a modular fork of the sjcl.codec.utf8String namespace

License BSD or GPL 2.0permissive1 versions1 maintainers1 deps7 weekly dl

michaelrhodes/sjcl-codec-utf8-string

/ 100

Health

use with caution

[email protected] low health (42/100) — consider alternatives

Moderate health score (42/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

sjcl-bit-array

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/sjcl-codec-utf8-string