Is @sustainers/service-name-consts safe to use?

@sustainers/service-name-consts has no known vulnerabilities on the latest version (0.0.3). DepScope rates its health at 40/100 (high risk).

What is the latest version of @sustainers/service-name-consts?

The latest version of @sustainers/service-name-consts is 0.0.3, released 2019-10-26.

Does @sustainers/service-name-consts have known vulnerabilities?

No known vulnerabilities on the latest version of @sustainers/service-name-consts.

Is @sustainers/service-name-consts deprecated?

No, @sustainers/service-name-consts is actively maintained. Latest release: 0.0.3 (2019-10-26).

What are alternatives to @sustainers/service-name-consts?

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

What license does @sustainers/service-name-consts use?

License information for @sustainers/service-name-consts is not declared in the registry metadata.

@sustainers/service-name-consts

npmv0.0.3

Constants that confine a service name.

3 versions2 maintainers0 deps31 weekly dl

/ 100

Health

use with caution

@sustainers/[email protected] low health (40/100) — consider alternatives

Moderate health score (40/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

3/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/@sustainers/service-name-consts