Is doorkeeper-jwt safe to use?

doorkeeper-jwt has no known vulnerabilities on the latest version (0.4.2). DepScope rates its health at 56/100 (high risk).

What is the latest version of doorkeeper-jwt?

The latest version of doorkeeper-jwt is 0.4.2, released 2024-08-12.

Does doorkeeper-jwt have known vulnerabilities?

No known vulnerabilities on the latest version of doorkeeper-jwt.

Is doorkeeper-jwt deprecated?

No, doorkeeper-jwt is actively maintained. Latest release: 0.4.2 (2024-08-12).

What are alternatives to doorkeeper-jwt?

Popular alternatives to doorkeeper-jwt in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does doorkeeper-jwt use?

doorkeeper-jwt is licensed under MIT.

doorkeeper-jwt

rubygemsv0.4.2

JWT token generator extension for Doorkeeper

License MITpermissive14 versions1 deps1,538,290 weekly dl

chriswarren/doorkeeper-jwt

/ 100

Health

safe to use

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

Health breakdown0 – 100

5/25

maintenance

17/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

jwt

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/doorkeeper-jwt