Is subschema-resolver-error safe to use?

subschema-resolver-error has no known vulnerabilities on the latest version (4.1.3). DepScope rates its health at 40/100 (high risk).

What is the latest version of subschema-resolver-error?

The latest version of subschema-resolver-error is 4.1.3, released 2019-10-14.

Does subschema-resolver-error have known vulnerabilities?

No known vulnerabilities on the latest version of subschema-resolver-error.

Is subschema-resolver-error deprecated?

No, subschema-resolver-error is actively maintained. Latest release: 4.1.3 (2019-10-14).

What are alternatives to subschema-resolver-error?

Popular alternatives to subschema-resolver-error in npm include: semver, minimatch, ansi-styles, debug, brace-expansion.

What license does subschema-resolver-error use?

subschema-resolver-error is licensed under MIT.

subschema-resolver-error

npmv4.1.3

Listens to errors at the resolved path. The path is resolved either by the path of the field, or the string that is used to configure. The recieving component will only get the first error.

License MITpermissive13 versions2 maintainers2 deps20 weekly dl

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

14.8 KBminified

4.7 KB gzipped

2 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

subschema-utils subschema-prop-types

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/subschema-resolver-error