Is browserify-bypass safe to use?

browserify-bypass has no known vulnerabilities on the latest version (0.1.0). DepScope rates its health at 42/100 (high risk).

What is the latest version of browserify-bypass?

The latest version of browserify-bypass is 0.1.0, released 2012-06-18.

Does browserify-bypass have known vulnerabilities?

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

Is browserify-bypass deprecated?

No, browserify-bypass is actively maintained. Latest release: 0.1.0 (2012-06-18).

What are alternatives to browserify-bypass?

Popular alternatives to browserify-bypass in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does browserify-bypass use?

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

browserify-bypass

npmv0.1.0

browserify middleware to declare alternative requires for the browser

1 versions1 maintainers0 deps

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

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-bypass