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

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

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

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

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

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

Is @mainsail/crypto-consensus-bls12-381 deprecated?

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

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

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

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

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

@mainsail/crypto-consensus-bls12-381

npmv0.0.1-alpha.20

Combined BLS12-381 utilities for the Mainsail blockchain

License GPL-3.0-only71 versions3 maintainers5 deps76 weekly dl

44

/ 100

Health

use with caution

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

Moderate health score (44/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

4/15

community

Vulnerabilities

0

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (5)

@mainsail/kernel @mainsail/container @mainsail/contracts @mainsail/crypto-key-pair-bls12-381 @mainsail/crypto-signature-bls12-381

API access

Get this data programmatically — free, no authentication.

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