Is @futureverse/signer safe to use?

@futureverse/signer has no known vulnerabilities on the latest version (1.8.0). DepScope rates its health at 49/100 (high risk).

What is the latest version of @futureverse/signer?

The latest version of @futureverse/signer is 1.8.0, released 2025-05-26.

Does @futureverse/signer have known vulnerabilities?

No known vulnerabilities on the latest version of @futureverse/signer.

Is @futureverse/signer deprecated?

No, @futureverse/signer is actively maintained. Latest release: 1.8.0 (2025-05-26).

What are alternatives to @futureverse/signer?

Popular alternatives to @futureverse/signer in npm include: ?, semver, debug, ansi-styles, brace-expansion.

What license does @futureverse/signer use?

License information for @futureverse/signer is not declared in the registry metadata.

@futureverse/signer

npmv1.8.0

Provides a signer interface with common methods for signing messages, transactions and extrinsics.

44 versions3 maintainers12 deps394 weekly dl

/ 100

Health

use with caution

@futureverse/[email protected] low health (49/100) — consider alternatives

Moderate health score (49/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

3/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 (12)

viem xrpl xumm blakejs @polkadot/api @polkadot/util @polkadot/types ripple-keypairs @polkadot/keyring ripple-binary-codec @polkadot/util-crypto @futureverse/signer-core

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@futureverse/signer