Is @mainsail/crypto-signature-schnorr-secp256k1 safe to use?

@mainsail/crypto-signature-schnorr-secp256k1 has no known vulnerabilities on the latest version (0.0.1-alpha.20). DepScope rates its health at 46/100 (high risk).

What is the latest version of @mainsail/crypto-signature-schnorr-secp256k1?

The latest version of @mainsail/crypto-signature-schnorr-secp256k1 is 0.0.1-alpha.20, released 2024-06-26.

Does @mainsail/crypto-signature-schnorr-secp256k1 have known vulnerabilities?

No known vulnerabilities on the latest version of @mainsail/crypto-signature-schnorr-secp256k1.

Is @mainsail/crypto-signature-schnorr-secp256k1 deprecated?

No, @mainsail/crypto-signature-schnorr-secp256k1 is actively maintained. Latest release: 0.0.1-alpha.20 (2024-06-26).

What are alternatives to @mainsail/crypto-signature-schnorr-secp256k1?

Popular alternatives to @mainsail/crypto-signature-schnorr-secp256k1 in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @mainsail/crypto-signature-schnorr-secp256k1 use?

@mainsail/crypto-signature-schnorr-secp256k1 is licensed under GPL-3.0-only.

@mainsail/crypto-signature-schnorr-secp256k1

npmv0.0.1-alpha.20

Schnorr (BIP340) signatures from libsecp256k1 for Mainsail blockchain

License GPL-3.0-only22 versions3 maintainers5 deps24 weekly dl

/ 100

Health

use with caution

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

Moderate health score (46/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

0/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 (5)

bcrypto @mainsail/utils @mainsail/kernel @mainsail/container @mainsail/contracts

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@mainsail/crypto-signature-schnorr-secp256k1