Is @mainsail/crypto-config safe to use?

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

What is the latest version of @mainsail/crypto-config?

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

Does @mainsail/crypto-config have known vulnerabilities?

No known vulnerabilities on the latest version of @mainsail/crypto-config.

Is @mainsail/crypto-config deprecated?

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

What are alternatives to @mainsail/crypto-config?

Popular alternatives to @mainsail/crypto-config in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @mainsail/crypto-config use?

@mainsail/crypto-config is licensed under GPL-3.0-only.

@mainsail/crypto-config

npmv0.0.1-alpha.20

Crypto configuration for the Mainsail blockchain

License GPL-3.0-only80 versions3 maintainers7 deps48 weekly dl

/ 100

Health

use with caution

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

Moderate health score (49/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

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

deepmerge lodash.get lodash.set lodash.clone @mainsail/kernel @mainsail/container @mainsail/contracts

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@mainsail/crypto-config