Is rpc-payload-id safe to use?

rpc-payload-id has no known vulnerabilities on the latest version (1.0.1). DepScope rates its health at 12/100 (critical risk).

What is the latest version of rpc-payload-id?

The latest version of rpc-payload-id is 1.0.1, released 2020-10-15.

Does rpc-payload-id have known vulnerabilities?

No known vulnerabilities on the latest version of rpc-payload-id.

Is rpc-payload-id deprecated?

Yes, rpc-payload-id is deprecated: Packaged deprecated in favor of @json-rpc-tools/utils Consider using ? instead.

What are alternatives to rpc-payload-id?

Popular alternatives to rpc-payload-id in npm include: ?, semver, minimatch, debug, ansi-styles.

What license does rpc-payload-id use?

rpc-payload-id is licensed under MIT.

rpc-payload-id

npmv1.0.1deprecated

JSON-RPC Time-based Random Payload ID

License MITpermissive2 versions1 maintainers0 deps455 weekly dl

pedrouid/rpc-payload-id

/ 100

Health

find alternative

rpc-payload-id is deprecated — find an alternative

Moderate health score (12/100) — verify manually
Package is deprecated

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

12/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/rpc-payload-id