Is @mainsail/crypto-key-pair-bls12-381 safe to use?

@mainsail/crypto-key-pair-bls12-381 has no known vulnerabilities on the latest version (0.0.1-alpha.20). DepScope rates its health at 52/100 (high risk).

What is the latest version of @mainsail/crypto-key-pair-bls12-381?

The latest version of @mainsail/crypto-key-pair-bls12-381 is 0.0.1-alpha.20, released 2024-06-26.

Does @mainsail/crypto-key-pair-bls12-381 have known vulnerabilities?

No known vulnerabilities on the latest version of @mainsail/crypto-key-pair-bls12-381.

Is @mainsail/crypto-key-pair-bls12-381 deprecated?

No, @mainsail/crypto-key-pair-bls12-381 is actively maintained. Latest release: 0.0.1-alpha.20 (2024-06-26).

What are alternatives to @mainsail/crypto-key-pair-bls12-381?

Popular alternatives to @mainsail/crypto-key-pair-bls12-381 in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @mainsail/crypto-key-pair-bls12-381 use?

@mainsail/crypto-key-pair-bls12-381 is licensed under GPL-3.0-only.

@mainsail/crypto-key-pair-bls12-381

npmv0.0.1-alpha.20

BLS12-381 key derivation for the Mainsail blockchain

License GPL-3.0-only75 versions3 maintainers9 deps112 weekly dl

/ 100

Health

use with caution

@mainsail/[email protected] low health (52/100) — consider alternatives

Moderate health score (52/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

3/20

popularity

25/25

security

15/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (9)

wif @scure/bip39 @chainsafe/bls @chainsafe/blst @mainsail/utils @mainsail/kernel bls12-381-keygen @mainsail/container @mainsail/contracts

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@mainsail/crypto-key-pair-bls12-381