Is @krentzen/buffer-reverse safe to use?

@krentzen/buffer-reverse has no known vulnerabilities on the latest version (1.0.3). DepScope rates its health at 40/100 (unknown risk).

What is the latest version of @krentzen/buffer-reverse?

The latest version of @krentzen/buffer-reverse is 1.0.3.

Does @krentzen/buffer-reverse have known vulnerabilities?

No known vulnerabilities on the latest version of @krentzen/buffer-reverse.

Is @krentzen/buffer-reverse deprecated?

No, @krentzen/buffer-reverse is actively maintained. Latest release: 1.0.3.

What are alternatives to @krentzen/buffer-reverse?

Popular alternatives to @krentzen/buffer-reverse in npm include: ?, semver, debug, ansi-styles, brace-expansion.

What license does @krentzen/buffer-reverse use?

@krentzen/buffer-reverse is licensed under MIT.

@krentzen/buffer-reverse

npmv1.0.3

A lite module for reverse-operations on buffers

License MIT0 versions0 deps136 weekly dl

crypto-browserify/buffer-reverse

/ 100

Health

do not use

Do not install. Package is flagged as malicious (advisory MAL-2026-6536).

Health breakdown0 – 100

Vulnerabilities

none known

⚠ Malicious package

This package is flagged as malicious by the OpenSSF/OSV community feed. Do not install.

Advisory: MAL-2026-6536 — Malicious code in @krentzen/buffer-reverse (npm)

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@krentzen/buffer-reverse