GKgkop·Aug 30, 2015
This is the counterpart for Ruby: https://github.com/twitter/secureheaders
In How widely used are security-based HTTP response headers?github
secure_headers
Ruby2013–2016
github / secure_headers
secure_headers
Manages application of security headers with many safe defaults
6Distinct people
6Mentions
0Explicit recommenders
3.2KGitHub stars
What to know before exploring
What it is
Manages application of security headers with many safe defaults
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year6 dated mentions
Observed mentions: 2013-01-23 16:49:21 UTC to 2016-10-24 16:01:52 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesSome ideas for a general strategy:
* Check TLS/SSL https://www.ssllabs.com/ssltest/
* Use Https, HSTS
* Have a security response page if someone found a problem
* What to do if your application was compromised, be prepared for the worst
* Check and update your software regularly
* Review changes in your software regularly if it impacts your overall security strategy
* Keep a security checklist in your codebase
* Do your own code audits, just read it again after a few days and ask the right questions
* Remove all credentials from your codebase
* Read about the "new" security headers here: https://github.com/twitter/secureheaders
* Know what kind of/how many requests your API/web app gets, maybe throttle or block some
In Ask HN: How do you take care of security risks at your startup?