Is browserify-zlib-next safe to use?

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

What is the latest version of browserify-zlib-next?

The latest version of browserify-zlib-next is 1.0.1, released 2017-01-23.

Does browserify-zlib-next have known vulnerabilities?

No known vulnerabilities on the latest version of browserify-zlib-next.

Is browserify-zlib-next deprecated?

No, browserify-zlib-next is actively maintained. Latest release: 1.0.1 (2017-01-23).

What are alternatives to browserify-zlib-next?

Popular alternatives to browserify-zlib-next in npm include: minimatch, wrap-ansi, @types/node, eslint-visitor-keys, ajv.

What license does browserify-zlib-next use?

browserify-zlib-next is licensed under MIT.

browserify-zlib-next

npmv1.0.1

Full zlib module for the browser

License MITpermissive2 versions1 maintainers1 deps475 weekly dl

ipfs/browserify-zlib-next

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

50.4 KBminified

15.4 KB gzipped

1 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

pako

API access

Get this data programmatically — free, no authentication.

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