Is uint8-encoding safe to use?

uint8-encoding has no known vulnerabilities on the latest version (2.0.1). DepScope rates its health at 41/100 (high risk).

What is the latest version of uint8-encoding?

The latest version of uint8-encoding is 2.0.1, released 2025-01-15.

Does uint8-encoding have known vulnerabilities?

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

Is uint8-encoding deprecated?

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

What are alternatives to uint8-encoding?

Popular alternatives to uint8-encoding in npm include: debug, semver, ansi-styles, minimatch, brace-expansion.

What license does uint8-encoding use?

uint8-encoding is licensed under MIT.

uint8-encoding

npmv2.0.1

Uint8 encoding, a simple way to convert strings to Uint8Arrays and vice versa.

License MITpermissive3 versions1 maintainers0 deps

fabiospampinato/uint8-encoding

/ 100

Health

safe to use

[email protected] is safe to use (health: 41/100)

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

9/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/uint8-encoding