Is @isaacs/buffer-to-string safe to use?

@isaacs/buffer-to-string has no known vulnerabilities on the latest version (1.0.1). DepScope rates its health at 45/100 (high risk).

What is the latest version of @isaacs/buffer-to-string?

The latest version of @isaacs/buffer-to-string is 1.0.1, released 2025-11-02.

No known vulnerabilities on the latest version of @isaacs/buffer-to-string.

No, @isaacs/buffer-to-string is actively maintained. Latest release: 1.0.1 (2025-11-02).

Popular alternatives to @isaacs/buffer-to-string in npm include: minimatch, chalk, commander, eslint-visitor-keys, ajv.

@isaacs/buffer-to-string is licensed under BlueOak-1.0.0.

npmv1.0.1

A better Buffer.toString()

License BlueOak-1.0.0permissive2 versions1 maintainers0 deps

/ 100

Health

safe to use

@isaacs/[email protected] is safe to use (health: 45/100)

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

🌟

10/10typed

bundled

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@isaacs/buffer-to-string