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

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

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

The latest version of @blossm/service-name-consts is 0.0.5, released 2025-06-20.

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

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

Is @blossm/service-name-consts deprecated?

No, @blossm/service-name-consts is actively maintained. Latest release: 0.0.5 (2025-06-20).

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

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

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

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

@blossm/service-name-consts

npmv0.0.5

Constants that confine a service name.

5 versions1 maintainers0 deps

/ 100

Health

safe to use

@blossm/[email protected] is safe to use (health: 49/100)

Health breakdown0 – 100

10/25

maintenance

0/20

popularity

25/25

security

12/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/@blossm/service-name-consts