Is int32-encoding safe to use?

int32-encoding has no known vulnerabilities on the latest version (1.0.1). DepScope rates its health at 43/100 (high risk).

What is the latest version of int32-encoding?

The latest version of int32-encoding is 1.0.1, released 2025-01-15.

Does int32-encoding have known vulnerabilities?

No known vulnerabilities on the latest version of int32-encoding.

Is int32-encoding deprecated?

No, int32-encoding is actively maintained. Latest release: 1.0.1 (2025-01-15).

What are alternatives to int32-encoding?

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

What license does int32-encoding use?

int32-encoding is licensed under MIT.

int32-encoding

npmv1.0.1

Int32 encoding, a simple way to convert 32-bit signed integers to Uint8Arrays, and vice versa.

License MITpermissive2 versions1 maintainers0 deps11,534 weekly dl

fabiospampinato/int32-encoding

/ 100

Health

use with caution

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

Moderate health score (43/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/int32-encoding