Is require-package-name safe to use?

require-package-name has no known vulnerabilities on the latest version (2.0.1). DepScope rates its health at 59/100 (high risk).

What is the latest version of require-package-name?

The latest version of require-package-name is 2.0.1, released 2015-05-07.

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

No, require-package-name is actively maintained. Latest release: 2.0.1 (2015-05-07).

Popular alternatives to require-package-name in npm include: minimatch, wrap-ansi, @types/node, eslint-visitor-keys, ajv.

require-package-name is licensed under MIT.

npmv2.0.1

gets the package name for a require statement

License MITpermissive3 versions1 maintainers0 deps2,358,895 weekly dl

/ 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

🌟

0/10untyped

No type definitions available

Quality signals

Publish security

npm signed

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/require-package-name