Is uglify-to-browserify safe to use?

uglify-to-browserify has no known vulnerabilities on the latest version (2.1.0). DepScope rates its health at 59/100 (high risk).

What is the latest version of uglify-to-browserify?

The latest version of uglify-to-browserify is 2.1.0, released 2018-02-02.

Does uglify-to-browserify have known vulnerabilities?

No known vulnerabilities on the latest version of uglify-to-browserify.

Is uglify-to-browserify deprecated?

No, uglify-to-browserify is actively maintained. Latest release: 2.1.0 (2018-02-02).

What are alternatives to uglify-to-browserify?

Popular alternatives to uglify-to-browserify in npm include: semver, debug, minimatch, strip-ansi, ms.

What license does uglify-to-browserify use?

uglify-to-browserify is licensed under MIT.

uglify-to-browserify

npmv2.1.0

A transform to make UglifyJS work in browserify.

License MITpermissive6 versions1 maintainers0 deps2,060,793 weekly dl

ForbesLindesay/uglify-to-browserify

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

0.5 KBminified

0.3 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/uglify-to-browserify