Is convert-tsconfig-paths-to-webpack-aliases safe to use?

convert-tsconfig-paths-to-webpack-aliases has no known vulnerabilities on the latest version (0.9.2). DepScope rates its health at 45/100 (high risk).

What is the latest version of convert-tsconfig-paths-to-webpack-aliases?

The latest version of convert-tsconfig-paths-to-webpack-aliases is 0.9.2, released 2017-09-14.

Does convert-tsconfig-paths-to-webpack-aliases have known vulnerabilities?

No known vulnerabilities on the latest version of convert-tsconfig-paths-to-webpack-aliases.

Is convert-tsconfig-paths-to-webpack-aliases deprecated?

No, convert-tsconfig-paths-to-webpack-aliases is actively maintained. Latest release: 0.9.2 (2017-09-14).

What are alternatives to convert-tsconfig-paths-to-webpack-aliases?

Popular alternatives to convert-tsconfig-paths-to-webpack-aliases in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does convert-tsconfig-paths-to-webpack-aliases use?

convert-tsconfig-paths-to-webpack-aliases is licensed under MIT.

convert-tsconfig-paths-to-webpack-aliases

npmv0.9.2

Utility package to convert typescript paths notation to webpack aliases.

License MITpermissive3 versions1 maintainers0 deps8,797 weekly dl

marzelin/convert-tsconfig-paths-to-webpack-aliases

/ 100

Health

use with caution

[email protected] low health (45/100) — consider alternatives

Moderate health score (45/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/convert-tsconfig-paths-to-webpack-aliases