How August 2017 RubyGems Vulnerabilities were patched on Heroku
2 comments · security
- Comments2
–Rank now
#7Peak rank
1Days on list
42Score · 7d
Oct 31, 2026First seen
On Lobsters
security
- Score
- 2
- Comments
- 2
- Submitted by
- schneems
- Tags
- security
- Site
- schneems.com
Story details from Lobsters ↗ · linked article on schneems.com.
Trending history
How August 2017 RubyGems Vulnerabilities were patched on Heroku was first seen on Lobsters · Hottest on Oct 31, 2026. Since then it has appeared in 1 check on 1 different day. Its best position was #7 of 25, reached on Oct 31, 05:21 UTC. It dropped off the list after Oct 31, 05:21 UTC.
Rank history
Position on Lobsters · Hottest at every check (lower is better).
Last 14 days
Best rank per day (UTC).
7
Oct 18today
From the discussion
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
I had figured Heroku users are in a better position than most as far as this goes. Meta: You can mark yourself as the author of a submission. Unsure if you just missed that here (no big deal)
> You can mark yourself as the author of a submission Sorry, thought I did. Thanks for the reminder.
Questions
Is How August 2017 RubyGems Vulnerabilities were patched on Heroku trending on Lobsters right now?
Not at the moment. It was last on the list on Oct 31, 05:21 UTC, after 1 day of trending.
What is the highest rank How August 2017 RubyGems Vulnerabilities were patched on Heroku reached?
#7 on Lobsters · Hottest, on Oct 31, 05:21 UTC. Trendoday checks this list every 30 minutes.
How long has How August 2017 RubyGems Vulnerabilities were patched on Heroku been trending?
It was first seen on Oct 31, 2026 and has been on the list on 1 day (1 check) since.