Is @types/jwt-decode safe to use?

@types/jwt-decode has no known vulnerabilities on the latest version (3.1.0). DepScope rates its health at 46/100 (high risk).

What is the latest version of @types/jwt-decode?

The latest version of @types/jwt-decode is 3.1.0, released 2020-11-05.

Does @types/jwt-decode have known vulnerabilities?

No known vulnerabilities on the latest version of @types/jwt-decode.

Is @types/jwt-decode deprecated?

Yes, @types/jwt-decode is deprecated: This is a stub types definition. jwt-decode provides its own type definitions, so you do not need this installed. Consider using ? instead.

What are alternatives to @types/jwt-decode?

Popular alternatives to @types/jwt-decode in npm include: ?, semver, debug, ansi-styles, brace-expansion.

What license does @types/jwt-decode use?

@types/jwt-decode is licensed under MIT.

@types/jwt-decode

npmv3.1.0deprecated

Stub TypeScript definitions entry for jwt-decode, which provides its own types definitions

License MITpermissive16 versions1 maintainers1 deps424,094 weekly dl

auth0/jwt-decode

46

/ 100

Health

find alternative

@types/jwt-decode is deprecated — find an alternative

Moderate health score (46/100) — verify manually
Package is deprecated

Health breakdown0 – 100

15/25

maintenance

14/20

popularity

25/25

security

15/15

maturity

7/15

community

Vulnerabilities

0

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

jwt-decode

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@types/jwt-decode