Is browserify-bignum safe to use?

browserify-bignum has no known vulnerabilities on the latest version (1.3.0-2). DepScope rates its health at 52/100 (high risk).

What is the latest version of browserify-bignum?

The latest version of browserify-bignum is 1.3.0-2, released 2014-01-12.

Does browserify-bignum have known vulnerabilities?

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

Is browserify-bignum deprecated?

No, browserify-bignum is actively maintained. Latest release: 1.3.0-2 (2014-01-12).

What are alternatives to browserify-bignum?

Popular alternatives to browserify-bignum in npm include: semver, debug, minimatch, strip-ansi, lru-cache.

What license does browserify-bignum use?

License information for browserify-bignum is not declared in the registry metadata.

browserify-bignum

npmv1.3.0-2

A browserify implementation of node-bignum

3 versions1 maintainers0 deps53,476 weekly dl

innoying/browserify-bignum

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

12.6 KBminified

5.9 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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