Is @railway-effects/error safe to use?

@railway-effects/error has no known vulnerabilities on the latest version (0.0.1). DepScope rates its health at 33/100 (critical risk).

What is the latest version of @railway-effects/error?

The latest version of @railway-effects/error is 0.0.1, released 2024-07-15.

Does @railway-effects/error have known vulnerabilities?

No known vulnerabilities on the latest version of @railway-effects/error.

Is @railway-effects/error deprecated?

No, @railway-effects/error is actively maintained. Latest release: 0.0.1 (2024-07-15).

What are alternatives to @railway-effects/error?

Popular alternatives to @railway-effects/error in npm include: ?, semver, minimatch, ansi-styles, brace-expansion.

What license does @railway-effects/error use?

License information for @railway-effects/error is not declared in the registry metadata.

@railway-effects/error

npmv0.0.1

Standardized error handling.

2 versions1 maintainers0 deps

/ 100

Health

use with caution

@railway-effects/[email protected] low health (33/100) — consider alternatives

Moderate health score (33/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/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/@railway-effects/error