Is @springernature/brand-context safe to use?

@springernature/brand-context has no known vulnerabilities on the latest version (32.0.1). DepScope rates its health at 55/100 (high risk).

What is the latest version of @springernature/brand-context?

The latest version of @springernature/brand-context is 32.0.1, released 2025-09-24.

Does @springernature/brand-context have known vulnerabilities?

No known vulnerabilities on the latest version of @springernature/brand-context.

Is @springernature/brand-context deprecated?

No, @springernature/brand-context is actively maintained. Latest release: 32.0.1 (2025-09-24).

What are alternatives to @springernature/brand-context?

Popular alternatives to @springernature/brand-context in npm include: semver, minimatch, ansi-styles, debug, brace-expansion.

What license does @springernature/brand-context use?

@springernature/brand-context is licensed under MIT.

@springernature/brand-context

npmv32.0.1

Bootstrapping for all components and products

License MITpermissive134 versions23 maintainers0 deps

/ 100

Health

safe to use

@springernature/[email protected] is safe to use (health: 55/100)

Health breakdown0 – 100

10/25

maintenance

0/20

popularity

25/25

security

15/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/@springernature/brand-context