Welcome to my second (very late to be published) update as Ruby Central’s security engineer in residence, sponsored by AWS.
My goal is to write a short update every week, chronicling what I’ve been working on, and reminding myself that I was, in fact, productive.
This week, I focused on addressing some inbound security reports, wrapped up feature work on event logging, and started building a new tool to assist me in researching the gems that are a part of our ecosystem.
Can’t share the details here yet until the reports are disclosed, but trust me that I did work in this area.
Event logging is basically feature complete! In fact, the models are already in production. You can see some screenshots linked on the massive PR. Not too much to say here outside of what’s in the PR. I’ll write up the feature on the RubyGems blog once it’s live.
Now that I’ve been working on RubyGems.org for a while, I finally got around to making it slightly easier to build UI. As a part of my event logging work, I set up a component preview system using lookbook, which is a way to see what a component looks like in isolation from the rest of the app. This is a big win for me, as it makes it easier to iterate on UI changes without needing to navigate through the app to see them. Selfishly, it’s also helpful because it’s an easy way to get code coverage on my Phlex components.
Gem Research Tool
As part of my role as a security engineer, I need to be able to quickly research the gems that are a part of our ecosystem. I started building a tool to help me do that, and it’s already been helpful in my work. It’s a rails app backed by a sqlite database that ingests data both from the rubygems.org data dumps as well as directly from all the .gem files hosted on rubygems.org. This was a fun rabbit hole to hack on, and it already paid dividends while addressing some of the security reports that came in this week.