Is @stdlib/buffer-alloc-unsafe safe to use?

@stdlib/buffer-alloc-unsafe has no known vulnerabilities on the latest version (0.2.3). DepScope rates its health at 64/100 (moderate risk).

What is the latest version of @stdlib/buffer-alloc-unsafe?

The latest version of @stdlib/buffer-alloc-unsafe is 0.2.3, released 2026-02-07.

Does @stdlib/buffer-alloc-unsafe have known vulnerabilities?

No known vulnerabilities on the latest version of @stdlib/buffer-alloc-unsafe.

Is @stdlib/buffer-alloc-unsafe deprecated?

No, @stdlib/buffer-alloc-unsafe is actively maintained. Latest release: 0.2.3 (2026-02-07).

What are alternatives to @stdlib/buffer-alloc-unsafe?

Popular alternatives to @stdlib/buffer-alloc-unsafe in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does @stdlib/buffer-alloc-unsafe use?

@stdlib/buffer-alloc-unsafe is licensed under Apache-2.0.

@stdlib/buffer-alloc-unsafe

npmv0.2.3

Allocate a buffer having a specified number of bytes.

License Apache-2.0permissive12 versions4 maintainers5 deps2,232 weekly dl

git://github.com/stdlib-js/buffer-alloc-unsafe

/ 100

Health

safe to use

@stdlib/[email protected] is safe to use (health: 64/100)

Health breakdown0 – 100

20/25

maintenance

6/20

popularity

25/25

security

9/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (5)

@stdlib/assert-is-function @stdlib/assert-is-nonnegative-integer @stdlib/buffer-ctor @stdlib/string-format @stdlib/error-tools-fmtprodmsg

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@stdlib/buffer-alloc-unsafe