Is browserify-aes safe to use?

browserify-aes has no known vulnerabilities on the latest version (1.2.0). DepScope rates its health at 66/100 (moderate risk).

What is the latest version of browserify-aes?

The latest version of browserify-aes is 1.2.0, released 2018-04-03.

Does browserify-aes have known vulnerabilities?

No known vulnerabilities on the latest version of browserify-aes.

Is browserify-aes deprecated?

No, browserify-aes is actively maintained. Latest release: 1.2.0 (2018-04-03).

What are alternatives to browserify-aes?

Popular alternatives to browserify-aes in npm include: ?, semver, minimatch, debug, ansi-styles.

What license does browserify-aes use?

browserify-aes is licensed under MIT.

browserify-aes

npmv1.2.0

aes, for browserify

License MITpermissive27 versions5 maintainers6 deps11,461,596 weekly dl

crypto-browserify/browserify-aes

/ 100

Health

use with caution

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

Moderate health score (66/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

20/20

popularity

25/25

security

15/15

maturity

6/15

community

0/15

popularity_floor

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)

buffer-xor cipher-base create-hash evp_bytestokey inherits safe-buffer

API access

Get this data programmatically — free, no authentication.

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