Is rack-request-id safe to use?

rack-request-id has no known vulnerabilities on the latest version (0.0.4). DepScope rates its health at 42/100 (high risk).

What is the latest version of rack-request-id?

The latest version of rack-request-id is 0.0.4, released 2016-03-24.

Does rack-request-id have known vulnerabilities?

No known vulnerabilities on the latest version of rack-request-id.

Is rack-request-id deprecated?

No, rack-request-id is actively maintained. Latest release: 0.0.4 (2016-03-24).

What are alternatives to rack-request-id?

Popular alternatives to rack-request-id in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does rack-request-id use?

rack-request-id is licensed under MIT.

rack-request-id

rubygemsv0.0.4

Request ID Header

License MITpermissive4 versions0 deps397,352 weekly dl

anveo/rack-request-id

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/rack-request-id