Is nlcst-is-literal safe to use?

nlcst-is-literal has no known vulnerabilities on the latest version (3.0.0). DepScope rates its health at 43/100 (high risk).

What is the latest version of nlcst-is-literal?

The latest version of nlcst-is-literal is 3.0.0, released 2023-07-17.

No known vulnerabilities on the latest version of nlcst-is-literal.

No, nlcst-is-literal is actively maintained. Latest release: 3.0.0 (2023-07-17).

Popular alternatives to nlcst-is-literal in npm include: minimatch, wrap-ansi, @types/node, eslint-visitor-keys, ajv.

nlcst-is-literal is licensed under MIT.

npmv3.0.0

nlcst utility to check whether a node is meant literally

License MITpermissive11 versions2 maintainers3 deps

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

3/15

community

Vulnerabilities

none known

🌟

10/10typed

bundled

Dependencies (3)

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/nlcst-is-literal