Is @filecoin-shipyard/lotus-client-provider-browser safe to use?

@filecoin-shipyard/lotus-client-provider-browser has no known vulnerabilities on the latest version (1.1.1). DepScope rates its health at 45/100 (high risk).

Does @filecoin-shipyard/lotus-client-provider-browser have known vulnerabilities?

No known vulnerabilities on the latest version of @filecoin-shipyard/lotus-client-provider-browser.

Is @filecoin-shipyard/lotus-client-provider-browser deprecated?

No, @filecoin-shipyard/lotus-client-provider-browser is actively maintained. Latest release: 1.1.1 (2023-01-02).

What are alternatives to @filecoin-shipyard/lotus-client-provider-browser?

Popular alternatives to @filecoin-shipyard/lotus-client-provider-browser in npm include: ?, minimatch, debug, ansi-styles, brace-expansion.

What license does @filecoin-shipyard/lotus-client-provider-browser use?

@filecoin-shipyard/lotus-client-provider-browser is licensed under (Apache-2.0 AND MIT).

@filecoin-shipyard/lotus-client-provider-browser

npmv1.1.1

Lotus JS Client Web Browser Provider module

License (Apache-2.0 AND MIT)permissive21 versions11 maintainers0 deps311 weekly dl

filecoin-shipyard/js-lotus-client-provider-browser

/ 100

Health

use with caution

@filecoin-shipyard/[email protected] low health (45/100) — consider alternatives

Moderate health score (45/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

12/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@filecoin-shipyard/lotus-client-provider-browser