Is @blossm/node-external-token safe to use?

@blossm/node-external-token has no known vulnerabilities on the latest version (0.0.203). DepScope rates its health at 52/100 (high risk).

What is the latest version of @blossm/node-external-token?

The latest version of @blossm/node-external-token is 0.0.203, released 2025-08-21.

Does @blossm/node-external-token have known vulnerabilities?

No known vulnerabilities on the latest version of @blossm/node-external-token.

Is @blossm/node-external-token deprecated?

No, @blossm/node-external-token is actively maintained. Latest release: 0.0.203 (2025-08-21).

What are alternatives to @blossm/node-external-token?

Popular alternatives to @blossm/node-external-token in npm include: semver, ansi-styles, debug, minimatch, brace-expansion.

What license does @blossm/node-external-token use?

License information for @blossm/node-external-token is not declared in the registry metadata.

@blossm/node-external-token

npmv0.0.203

Creates a token for calling external services on behalf of the node.

199 versions1 maintainers2 deps

/ 100

Health

safe to use

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

Health breakdown0 – 100

10/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

@blossm/connection-token @blossm/gcp-secret

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@blossm/node-external-token