CLUSTER ICALENDAR-EVENTS-FILES · 5 ENTRIES · EARLIEST ENTRY 2015-11-23
iCalendar parsing and conversion tools
This cluster consists of tools that read, parse, display, or convert iCalendar data, including a desktop notifier, a Ruby library, a viewer, a terminal printer, and an exporter from TimeTree. The five dated entries are scattered across 2015, 2023, 2025, and 2026, with no consistent pattern; the cluster's dated history is too sparse to infer a trend. All traction leaders (timetree-exporter, ruby-icalendar, meeters-bin) have zero stars, so no product clearly leads on activity.
Entry timeline
ENTRY TIMELINE
Each bar is the month a member carries, which is a creation date where the source published one and a crawl date otherwise. Nothing in the index was found before 11 August 2026, and coverage broadened sharply on 14–15 August, so a bar from then on reports how much we found that month, not how much was built; an earlier bar reports how far back a member's own source dated it — not how long we have been watching.
Members by activity
Activity signals, not revenue.
Build origin · 1 hand-coded · 4 unlabelled
Operator · 5 open source
Two labels per entry, never collapsed into one: how it was built, and who stands behind it. Counted over the 5 listed below. Unlabelled means nothing has decided yet — not that the answer is small.
- 01timetree-exporter0★4 moliveopen sourceTool that exports events from TimeTree calendar to iCalendar format for use in other applications.
- 02ruby-icalendar0★1 yrabandonedliveopen sourceA Ruby library for reading and writing iCalendar data.
- 03meeters-bin0★1 yrabandonedliveopen sourceDesktop utility that watches an iCalendar file URL and sends notifications shortly before upcoming meetings.
- 04almanac0★3 yrabandonedliveopen sourceTerminal tool that parses iCalendar files and prints their events in a readable format.
- 05vcal0★8 yrabandonedlivehand-codedopen sourceDisplays data from vCalendar or iCalendar files.
Ranked by traction, highest first, and paged 20 at a time — this is a window on the cluster, never the whole of it. Ties are broken by a stable id so a product cannot appear on two pages or fall between them. Browse every cluster.