Is @nodesecure/sec-literal safe to use?

@nodesecure/sec-literal has no known vulnerabilities on the latest version (1.4.0). DepScope rates its health at 53/100 (high risk).

What is the latest version of @nodesecure/sec-literal?

The latest version of @nodesecure/sec-literal is 1.4.0, released 2025-11-11.

Does @nodesecure/sec-literal have known vulnerabilities?

No known vulnerabilities on the latest version of @nodesecure/sec-literal.

Is @nodesecure/sec-literal deprecated?

No, @nodesecure/sec-literal is actively maintained. Latest release: 1.4.0 (2025-11-11).

What are alternatives to @nodesecure/sec-literal?

Popular alternatives to @nodesecure/sec-literal in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does @nodesecure/sec-literal use?

@nodesecure/sec-literal is licensed under MIT.

@nodesecure/sec-literal

npmv1.4.0

Package created to analyze JavaScript literals

License MITpermissive6 versions4 maintainers3 deps

NodeSecure/js-x-ray

/ 100

Health

safe to use

@nodesecure/[email protected] is safe to use (health: 53/100)

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (3)

is-svg string-width frequency-set

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@nodesecure/sec-literal