npmpackage.info

Gathering detailed insights and metrics for browserify-aes

Other packages similar to browserify-aes

crypto-browserify

3.12.1

implementation of crypto for the browser

browserify-cipher

1.0.1

ciphers for the browser

ethereum-cryptography

3.0.0

All the cryptographic primitives used in Ethereum

evp_bytestokey

1.0.3

The insecure key derivation algorithm from OpenSSL

Gathering detailed insights and metrics for browserify-aes

browserify-aes

aes, for browserify

1.2.0

NOASSERTION

JavaScript

3,176,989,347 4.3

Installations

npm install browserify-aes

Score

91.3

Supply Chain

74.4

Quality

80.3

Maintenance

100

Vulnerability

99.6

License

Pull Requests

Open

5

Total

43

Closed

3

Merged

35

Issues

Open

5

Total

22

Closed

17

Releases

Unable to fetch releases

Developer

crypto-browserify

Developer Guide

BETA

Module System

CommonJS, UMD

Min. Node Version

Typescript Support

No

Node Version

8.11.1

NPM Version

5.8.0 Statistics

62 Stars

140 Commits

28 Forks

6 Watching

2 Branches

36 Contributors

Updated on 11 May 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

3,176,989,347

Last day

-25.3%

1,457,290

Compared to previous day

Last week

-4.4%

10,337,326

Compared to previous week

Last month

14.2%

43,066,071

Compared to previous month

Last year

-16.9%

449,096,382

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

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

Dev Dependencies

standard tap-spec tape

Versions

browserify-aes

Node style aes for use in the browser. Implements:

createCipher
createCipheriv
createDecipher
createDecipheriv
getCiphers

In node.js, the crypto implementation is used, in browsers it falls back to a pure JavaScript implementation.

EVP_BytesToKey is a straight up port of the same function from OpenSSL as there is literally no documenation on it beyond it using 'undocumented extensions' for longer keys.

LICENSES

Much of this library has been taken from the AES implementation in triplesec (apparently licensed MIT), which is a partial derivation of crypto-js, which is licensed BSD-3 clause, the relevant LICENSE text for both MIT and BSD-3 can be found in LICENSE.

Parts of ghash.js are a partial derivation of work by Juho Vähä-Herttua in SJCL, which is LICENSED BSD-2 || GPL-2, with the LICENSE text included inline in ghash.js.

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

Security-Policy

Determines if the project has published a security policy.

9

License

Determines if the project has defined a license.

3

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

4.3

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More