Is jwt_signed_request safe to use?

jwt_signed_request has no known vulnerabilities on the latest version (4.1.0). DepScope rates its health at 54/100 (high risk).

What is the latest version of jwt_signed_request?

The latest version of jwt_signed_request is 4.1.0, released 2025-06-25.

No known vulnerabilities on the latest version of jwt_signed_request.

No, jwt_signed_request is actively maintained. Latest release: 4.1.0 (2025-06-25).

Popular alternatives to jwt_signed_request in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

License information for jwt_signed_request is not declared in the registry metadata.

rubygemsv4.1.0

JWT request signing and verification for Internal APIs

20 versions2 deps61,083 weekly dl

/ 100

Health

safe to use

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

Health breakdown0 – 100

10/25

maintenance

10/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Dependencies (2)

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/jwt_signed_request