Is secure_headers safe to use?

secure_headers has no known vulnerabilities on the latest version (7.2.0). DepScope rates its health at 69/100 (moderate risk).

What is the latest version of secure_headers?

The latest version of secure_headers is 7.2.0, released 2026-02-20.

No known vulnerabilities on the latest version of secure_headers.

No, secure_headers is actively maintained. Latest release: 7.2.0 (2026-02-20).

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

secure_headers is licensed under MIT.

rubygemsv7.2.0

Add easily configured security headers to responses including content-security-policy, x-frame-options, strict-transport-security, etc.

License MITpermissive20 versions1 deps74,510 weekly dl

/ 100

Health

safe to use

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

Health breakdown0 – 100

20/25

maintenance

10/20

popularity

25/25

security

9/15

maturity

5/15

community

Vulnerabilities

none known

Dependencies (1)

API access

Get this data programmatically — free, no authentication.

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