Is @loke/http-rpc safe to use?

@loke/http-rpc has no known vulnerabilities on the latest version (5.10.2). DepScope rates its health at 67/100 (moderate risk).

What is the latest version of @loke/http-rpc?

The latest version of @loke/http-rpc is 5.10.2, released 2026-06-09.

Does @loke/http-rpc have known vulnerabilities?

No known vulnerabilities on the latest version of @loke/http-rpc.

Is @loke/http-rpc deprecated?

No, @loke/http-rpc is actively maintained. Latest release: 5.10.2 (2026-06-09).

What are alternatives to @loke/http-rpc?

Popular alternatives to @loke/http-rpc in npm include: ?, semver, debug, ansi-styles, brace-expansion.

What license does @loke/http-rpc use?

License information for @loke/http-rpc is not declared in the registry metadata.

@loke/http-rpc

npmv5.10.2

- createRequestHandler now accepts a list of services. - The root endpoint on a request handler now returns an array of metadata for each service - Legacy mode can be enabled to still handle calls in the older `/methodName` format. - It is now preferred t

25 versions3 maintainers3 deps1,303 weekly dl

LOKE/loke-http-rpc

/ 100

Health

use with caution

@loke/[email protected] low health (67/100) — consider alternatives

Moderate health score (67/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

@loke/context ajv on-finished

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@loke/http-rpc