Is @667/express-jwt-authz safe to use?

@667/express-jwt-authz has no known vulnerabilities on the latest version (2.4.1-1). DepScope rates its health at 39/100 (critical risk).

What is the latest version of @667/express-jwt-authz?

The latest version of @667/express-jwt-authz is 2.4.1-1, released 2021-03-23.

Does @667/express-jwt-authz have known vulnerabilities?

No known vulnerabilities on the latest version of @667/express-jwt-authz.

Is @667/express-jwt-authz deprecated?

No, @667/express-jwt-authz is actively maintained. Latest release: 2.4.1-1 (2021-03-23).

What are alternatives to @667/express-jwt-authz?

Popular alternatives to @667/express-jwt-authz in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @667/express-jwt-authz use?

@667/express-jwt-authz is licensed under MIT.

@667/express-jwt-authz

npmv2.4.1-1

Validate a JWTs scope to authorize access to an endpoint

License MITpermissive2 versions1 maintainers0 deps12 weekly dl

june07/express-jwt-authz

/ 100

Health

use with caution

@667/[email protected] low health (39/100) — consider alternatives

Moderate health score (39/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.1 KBminified

0.6 KB gzipped

0 direct dependencies

side effectsscoped

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@667/express-jwt-authz