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 53/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.

Does nlcst-is-literal have known vulnerabilities?

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

Is nlcst-is-literal deprecated?

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

What are alternatives to nlcst-is-literal?

Popular alternatives to nlcst-is-literal in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does nlcst-is-literal use?

nlcst-is-literal is licensed under MIT.

nlcst-is-literal

npmv3.0.0

nlcst utility to check whether a node is meant literally

License MITpermissive11 versions2 maintainers3 deps91,457 weekly dl

syntax-tree/nlcst-is-literal

/ 100

Health

use with caution

[email protected] low health (53/100) — consider alternatives

Moderate health score (53/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

15/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

@types/nlcst @types/unist nlcst-to-string

API access

Get this data programmatically — free, no authentication.

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