Is @sealsystems/service-protocol safe to use?

@sealsystems/service-protocol has no known vulnerabilities on the latest version (2.1.0). DepScope rates its health at 38/100 (critical risk).

What is the latest version of @sealsystems/service-protocol?

The latest version of @sealsystems/service-protocol is 2.1.0, released 2024-03-26.

Does @sealsystems/service-protocol have known vulnerabilities?

No known vulnerabilities on the latest version of @sealsystems/service-protocol.

Is @sealsystems/service-protocol deprecated?

No, @sealsystems/service-protocol is actively maintained. Latest release: 2.1.0 (2024-03-26).

What are alternatives to @sealsystems/service-protocol?

Popular alternatives to @sealsystems/service-protocol in npm include: semver, minimatch, debug, ansi-styles, brace-expansion.

What license does @sealsystems/service-protocol use?

@sealsystems/service-protocol is licensed under MIT.

@sealsystems/service-protocol

npmv2.1.0

Determine protocol for connecting to service

License MITpermissive5 versions3 maintainers1 deps14 weekly dl

sealsystems/node-service-protocol

/ 100

Health

use with caution

@sealsystems/[email protected] low health (38/100) — consider alternatives

Moderate health score (38/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

@sealsystems/seal-getenv

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@sealsystems/service-protocol