Is buffer-to-string safe to use?

buffer-to-string has no known vulnerabilities on the latest version (0.1.0). DepScope rates its health at 62/100 (moderate risk).

What is the latest version of buffer-to-string?

The latest version of buffer-to-string is 0.1.0, released 2016-01-16.

Does buffer-to-string have known vulnerabilities?

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

Is buffer-to-string deprecated?

No, buffer-to-string is actively maintained. Latest release: 0.1.0 (2016-01-16).

What are alternatives to buffer-to-string?

Popular alternatives to buffer-to-string in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does buffer-to-string use?

buffer-to-string is licensed under MIT.

buffer-to-string

npmv0.1.0

A better Buffer.toString()

License MITpermissive1 versions1 maintainers0 deps2 weekly dl

tapjs/buffer-to-string

/ 100

Health

use with caution

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

Moderate health score (62/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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