Is @jscpd/tokenizer safe to use?

@jscpd/tokenizer has no known vulnerabilities on the latest version (4.0.5). DepScope rates its health at 69/100 (moderate risk).

What is the latest version of @jscpd/tokenizer?

The latest version of @jscpd/tokenizer is 4.0.5, released 2026-04-10.

No known vulnerabilities on the latest version of @jscpd/tokenizer.

No, @jscpd/tokenizer is actively maintained. Latest release: 4.0.5 (2026-04-10).

Popular alternatives to @jscpd/tokenizer in npm include: debug, chalk, picomatch, source-map, has-flag.

@jscpd/tokenizer is licensed under MIT.

npmv4.0.5

tokenizer of source code for jscpd

License MITpermissive29 versions1 maintainers3 deps

/ 100

Health

safe to use

@jscpd/[email protected] is safe to use (health: 69/100)

Health breakdown0 – 100

25/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

7/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/@jscpd/tokenizer