Is @klever/connect-encoding safe to use?

@klever/connect-encoding has no known vulnerabilities on the latest version (0.1.3). DepScope rates its health at 47/100 (high risk).

What is the latest version of @klever/connect-encoding?

The latest version of @klever/connect-encoding is 0.1.3, released 2026-03-01.

Does @klever/connect-encoding have known vulnerabilities?

No known vulnerabilities on the latest version of @klever/connect-encoding.

Is @klever/connect-encoding deprecated?

No, @klever/connect-encoding is actively maintained. Latest release: 0.1.3 (2026-03-01).

What are alternatives to @klever/connect-encoding?

Popular alternatives to @klever/connect-encoding in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @klever/connect-encoding use?

@klever/connect-encoding is licensed under MIT.

@klever/connect-encoding

npmv0.1.3

Encoding and decoding utilities for Klever Connect SDK

License MITpermissive4 versions4 maintainers2 deps

klever-io/klever-connect

/ 100

Health

use with caution

@klever/[email protected] low health (47/100) — consider alternatives

Moderate health score (47/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (2)

@noble/hashes @scure/base

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@klever/connect-encoding