Is @keystone-next/fields safe to use?

@keystone-next/fields has no known vulnerabilities on the latest version (15.0.0). DepScope rates its health at 13/100 (critical risk).

What is the latest version of @keystone-next/fields?

The latest version of @keystone-next/fields is 15.0.0, released 2021-09-06.

Does @keystone-next/fields have known vulnerabilities?

No known vulnerabilities on the latest version of @keystone-next/fields.

Is @keystone-next/fields deprecated?

Yes, @keystone-next/fields is deprecated: Keystone Next has graduated to the @keystone-6 namespace; for more information see https://keystonejs.com/updates/general-availability Consider using ? instead.

What are alternatives to @keystone-next/fields?

Popular alternatives to @keystone-next/fields in npm include: ?, semver, minimatch, debug, ansi-styles.

What license does @keystone-next/fields use?

@keystone-next/fields is licensed under MIT.

@keystone-next/fields

npmv15.0.0deprecated

The exports of this package have been moved to `@keystone-next/keystone/fields`.

License MITpermissive36 versions2 maintainers0 deps138 weekly dl

keystonejs/keystone

/ 100

Health

find alternative

@keystone-next/fields is deprecated — find an alternative

Moderate health score (13/100) — verify manually
Package is deprecated

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@keystone-next/fields