Is sodium-browserify-tweetnacl safe to use?

sodium-browserify-tweetnacl has no known vulnerabilities on the latest version (0.2.6). DepScope rates its health at 48/100 (high risk).

What is the latest version of sodium-browserify-tweetnacl?

The latest version of sodium-browserify-tweetnacl is 0.2.6, released 2019-04-19.

Does sodium-browserify-tweetnacl have known vulnerabilities?

No known vulnerabilities on the latest version of sodium-browserify-tweetnacl.

Is sodium-browserify-tweetnacl deprecated?

No, sodium-browserify-tweetnacl is actively maintained. Latest release: 0.2.6 (2019-04-19).

What are alternatives to sodium-browserify-tweetnacl?

Popular alternatives to sodium-browserify-tweetnacl in npm include: debug, minimatch, strip-ansi, ms, lru-cache.

What license does sodium-browserify-tweetnacl use?

sodium-browserify-tweetnacl is licensed under MIT.

sodium-browserify-tweetnacl

npmv0.2.6

wraps javascript port of [tweetnacl](https://github.com/dchest/tweetnacl-js) with the api of [chloride](https://github.com/dominictarr/chloride) as an alternative to [sodium-browserify](https://github.com/dominictarr/sodium-browserify) that has a much muc

License MITpermissive10 versions1 maintainers5 deps3,075 weekly dl

git://github.com/dominictarr/sodium-browserify-tweetnacl

/ 100

Health

safe to use

[email protected] is safe to use (health: 48/100)

Health breakdown0 – 100

0/25

maintenance

6/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 (5)

chloride-test ed2curve sha.js tweetnacl tweetnacl-auth

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/sodium-browserify-tweetnacl