A DIRECT LINE TO YOUR APPLICATION
A small signal.
A useful head start.
Rails CVE checks the Rails maintainers’ advisories every five minutes and tells you when one is published, updated, or withdrawn. Each notification carries the exact affected versions and an investigation brief for your coding agent.
Two ways to be notified
| Channel | What you get | Setup |
|---|---|---|
| A plain message with the advisory summary and the full investigation brief. | Verify an address. Nothing to build. | |
| Webhook | A signed JSON event posted to an HTTPS endpoint you control. | A small receiver, a signing secret, and a one-time handshake. |
| Both | Both channels, retried independently. | Both of the above. |
Quick start
- Create a workspace
Open Connect. Continue with GitHub, or create a workspace and save the management token it shows you once.
- Verify an email address
In Settings, add an address and confirm it from the email that arrives. Skip this if you only want webhooks.
- Add an app
Name it after the codebase, choose email, webhook, or both, and pick your verified address or enter your endpoint URL. Ten apps per workspace.
- Verify a webhook
Save the signing secret in your receiver, then click Verify webhook. Your receiver echoes a signed challenge once and the app goes active.
- Send a test
A test event arrives within a few minutes and says clearly that it is not an advisory. Watch it land in the delivery log.
What arrives
When Rails publishes, updates, or withdraws an advisory, every active app gets one notification. An email contains the app name, advisory title, severity, canonical link, and the complete investigation brief. A webhook receives a signed JSON event with the full advisory, exact affected and patched ranges, the brief, and a link to download it as SKILL.md.
See a complete example event →
Verify before you trust
Every webhook request is signed with HMAC-SHA256 over the timestamp and the exact body. Verify the signature first, echo the ownership challenge once, store events by ID, and return 2xx. The Rails receiver example does all of it in one controller. Details are in the webhook contract.
From signal to investigation
Open any advisory to copy its investigation brief or download SKILL.md. Run it with your coding agent from inside the repository. The brief asks for installed versions, file-level evidence, a verdict, and a proposed fix for your review. It requires your approval before any change. See Coding agents.
What is covered
The source is the published security advisories in rails/rails. Other gems are not included. New subscriptions receive future events; the archive stays browsable in the advisory index. Receiving an advisory does not mean your app is affected, and nothing runs in your environment unless you set it up.
Retries and availability
Deliveries are attempted up to eight times over roughly a day, with a ten-second timeout for webhooks. Delivery is at least once and unordered, so receivers must deduplicate. A bounded batch runs every five minutes. This is an independent community service with no delivery-time guarantee; keep your existing security monitoring.
Open interfaces
The public JSON feed lists every advisory. /api/advisories/:id returns one advisory and its brief by GHSA or CVE ID. /api/health reports the last successful sync. The source is MIT licensed.