Is plugin-name-to-package-name safe to use?

plugin-name-to-package-name has no known vulnerabilities on the latest version (0.1.1). DepScope rates its health at 39/100 (critical risk).

What is the latest version of plugin-name-to-package-name?

The latest version of plugin-name-to-package-name is 0.1.1, released 2020-05-03.

Does plugin-name-to-package-name have known vulnerabilities?

No known vulnerabilities on the latest version of plugin-name-to-package-name.

Is plugin-name-to-package-name deprecated?

No, plugin-name-to-package-name is actively maintained. Latest release: 0.1.1 (2020-05-03).

What are alternatives to plugin-name-to-package-name?

Popular alternatives to plugin-name-to-package-name in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does plugin-name-to-package-name use?

plugin-name-to-package-name is licensed under MIT.

plugin-name-to-package-name

npmv0.1.1

Utility to transform plugin names into package names as seen at e.g. eslint, stricter, and others

License MITpermissive2 versions1 maintainers0 deps

obweger/plugin-name-to-package-name

/ 100

Health

use with caution

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

Low health score (39/100)

Health breakdown0 – 100

0/25

maintenance

0/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/plugin-name-to-package-name