Is pkg-with-failing-optional-dependency safe to use?

pkg-with-failing-optional-dependency has no known vulnerabilities on the latest version (1.0.1). DepScope rates its health at 45/100 (high risk).

What is the latest version of pkg-with-failing-optional-dependency?

The latest version of pkg-with-failing-optional-dependency is 1.0.1, released 2016-07-16.

Does pkg-with-failing-optional-dependency have known vulnerabilities?

No known vulnerabilities on the latest version of pkg-with-failing-optional-dependency.

Is pkg-with-failing-optional-dependency deprecated?

No, pkg-with-failing-optional-dependency is actively maintained. Latest release: 1.0.1 (2016-07-16).

What are alternatives to pkg-with-failing-optional-dependency?

Popular alternatives to pkg-with-failing-optional-dependency in npm include: semver, ms, lru-cache, supports-color, ansi-regex.

What license does pkg-with-failing-optional-dependency use?

pkg-with-failing-optional-dependency is licensed under MIT.

pkg-with-failing-optional-dependency

npmv1.0.1

A package that has a failing optional dependency

License MITpermissive2 versions1 maintainers2 deps1,080 weekly dl

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

0.3 KBminified

0.2 KB gzipped

1 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

is-negative pkg-with-failing-postinstall

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/pkg-with-failing-optional-dependency