Is registry-auth-token safe to use?

registry-auth-token has no known vulnerabilities on the latest version (5.1.1). DepScope rates its health at 80/100 (low risk).

What is the latest version of registry-auth-token?

The latest version of registry-auth-token is 5.1.1, released 2026-01-16.

Does registry-auth-token have known vulnerabilities?

No known vulnerabilities on the latest version of registry-auth-token.

Is registry-auth-token deprecated?

No, registry-auth-token is actively maintained. Latest release: 5.1.1 (2026-01-16).

What are alternatives to registry-auth-token?

Popular alternatives to registry-auth-token in npm include: ?, ansi-styles, semver, brace-expansion, ms.

What license does registry-auth-token use?

registry-auth-token is licensed under MIT.

registry-auth-token

npmv5.1.1

Get the auth token set for an npm registry (if any)

License MITpermissive28 versions3 maintainers1 deps22,947,651 weekly dl

rexxars/registry-auth-token

/ 100

Health

safe to use

[email protected] is safe to use (health: 80/100)

Health breakdown0 – 100

15/25

maintenance

20/20

popularity

25/25

security

15/15

maturity

5/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Quality signals

Download trend

stable(0%)

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (1)

@pnpm/npm-conf

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/registry-auth-token