Is @aws-sdk/crypto-sha256-js safe to use?

@aws-sdk/crypto-sha256-js has no known vulnerabilities on the latest version (0.1.0-preview.1). DepScope rates its health at 46/100 (high risk).

What is the latest version of @aws-sdk/crypto-sha256-js?

The latest version of @aws-sdk/crypto-sha256-js is 0.1.0-preview.1, released 2018-11-19.

Does @aws-sdk/crypto-sha256-js have known vulnerabilities?

No known vulnerabilities on the latest version of @aws-sdk/crypto-sha256-js.

Is @aws-sdk/crypto-sha256-js deprecated?

No, @aws-sdk/crypto-sha256-js is actively maintained. Latest release: 0.1.0-preview.1 (2018-11-19).

What are alternatives to @aws-sdk/crypto-sha256-js?

Popular alternatives to @aws-sdk/crypto-sha256-js in npm include: semver, ansi-styles, debug, minimatch, brace-expansion.

What license does @aws-sdk/crypto-sha256-js use?

@aws-sdk/crypto-sha256-js is licensed under Apache-2.0.

@aws-sdk/crypto-sha256-js

npmv0.1.0-preview.1

License Apache-2.0permissive1 versions2 maintainers3 deps1,488 weekly dl

/ 100

Health

safe to use

@aws-sdk/[email protected] is safe to use (health: 46/100)

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

tslib @aws-sdk/types @aws-sdk/util-utf8-browser

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@aws-sdk/crypto-sha256-js