Is public-encrypt safe to use?

public-encrypt has no known vulnerabilities on the latest version (4.0.3). DepScope rates its health at 45/100 (high risk).

What is the latest version of public-encrypt?

The latest version of public-encrypt is 4.0.3, released 2018-10-01.

Does public-encrypt have known vulnerabilities?

No known vulnerabilities on the latest version of public-encrypt.

Is public-encrypt deprecated?

No, public-encrypt is actively maintained. Latest release: 4.0.3 (2018-10-01).

What are alternatives to public-encrypt?

Popular alternatives to public-encrypt in npm include: debug, chalk, picomatch, source-map, has-flag.

What license does public-encrypt use?

public-encrypt is licensed under MIT.

public-encrypt

npmv4.0.3

browserify version of publicEncrypt & privateDecrypt

License MITpermissive11 versions5 maintainers6 deps

crypto-browserify/publicEncrypt

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Quality signals

Download trend

stable(0%)

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (6)

bn.js browserify-rsa create-hash parse-asn1 randombytes safe-buffer

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/public-encrypt