Is @fl-did-registry/jwt safe to use?

@fl-did-registry/jwt has no known vulnerabilities on the latest version (0.5.2). DepScope rates its health at 36/100 (critical risk).

What is the latest version of @fl-did-registry/jwt?

The latest version of @fl-did-registry/jwt is 0.5.2, released 2021-09-13.

Does @fl-did-registry/jwt have known vulnerabilities?

No known vulnerabilities on the latest version of @fl-did-registry/jwt.

Is @fl-did-registry/jwt deprecated?

No, @fl-did-registry/jwt is actively maintained. Latest release: 0.5.2 (2021-09-13).

What are alternatives to @fl-did-registry/jwt?

Popular alternatives to @fl-did-registry/jwt in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @fl-did-registry/jwt use?

@fl-did-registry/jwt is licensed under GPL-3.0-or-later.

@fl-did-registry/jwt

npmv0.5.2

The package manages JWTs

License GPL-3.0-or-later3 versions1 maintainers9 deps7 weekly dl

/ 100

Health

use with caution

@fl-did-registry/[email protected] low health (36/100) — consider alternatives

Moderate health score (36/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (9)

@fl-did-registry/keys @types/jsonwebtoken @types/promise.allsettled base64url ethereumjs-util ethers jsonwebtoken key-encoder promise.allsettled

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@fl-did-registry/jwt