Is @codingame/json-rpc-2.0 safe to use?

@codingame/json-rpc-2.0 has no known vulnerabilities on the latest version (1.7.0-next.1). DepScope rates its health at 41/100 (high risk).

What is the latest version of @codingame/json-rpc-2.0?

The latest version of @codingame/json-rpc-2.0 is 1.7.0-next.1, released 2024-11-27.

Does @codingame/json-rpc-2.0 have known vulnerabilities?

No known vulnerabilities on the latest version of @codingame/json-rpc-2.0.

Is @codingame/json-rpc-2.0 deprecated?

No, @codingame/json-rpc-2.0 is actively maintained. Latest release: 1.7.0-next.1 (2024-11-27).

What are alternatives to @codingame/json-rpc-2.0?

Popular alternatives to @codingame/json-rpc-2.0 in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does @codingame/json-rpc-2.0 use?

@codingame/json-rpc-2.0 is licensed under MIT.

@codingame/json-rpc-2.0

npmv1.7.0-next.1

JSON-RPC 2.0 client and server

License MITpermissive1 versions5 maintainers0 deps

shogowada/json-rpc-2.0

/ 100

Health

safe to use

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

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

5/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/@codingame/json-rpc-2.0