leafac/kill-the-newsletter

Convert email newsletters into Atom feeds

View on GitHub ↗Jump to charts ↓

leafac/kill-the-newsletter has 3k+ stars and 100+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 3, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 34 minutes ago
Added to GitGenius on September 22nd, 2026
Created on May 9th, 2018
Open Issues & Pull Requests: 15 (+0)
GitHub issues: Enabled
Number of forks: 145
Total Stargazers: 3,112 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.9 days
Mean response time: 35.8 days
90th percentile: 58.4 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 293 days
Stale 30+ days: 6
Stale 90+ days: 5

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kill the Newsletter is a service that converts email newsletters into Atom feeds.

The problem it solves is the fragmentation of newsletter consumption across email inboxes, which makes it difficult to manage subscriptions alongside other content feeds. The tool works by generating a unique email address for each newsletter subscription. When newsletters arrive at that address, the service parses them and publishes the content as entries in an Atom feed, allowing users to read newsletters in their feed reader of choice rather than in email.

The service suits anyone who prefers centralized feed reading over email management, particularly those already using feed readers for other content. It works well for newsletters that are primarily text or HTML content without complex interactive elements. The tool is offered as a hosted service at its homepage, removing the need for self-hosting for most users, though deployment and development guides are available for those who want to run their own instance.

The project maintains active development with regular commits addressing bug fixes and feature improvements. The codebase shows consistent attention to code quality through refactoring and cleanup work. The maintainer engages with user feedback and issues, responding to problems and incorporating suggestions into updates.