Deal Teardown: Abandoned iCal Recurrence Library With 2,450 Stars — Asking $4,300

How ReviveHQ Found This Deal

rrule.js — a JavaScript implementation of the iCalendar RRULE specification for recurring events — surfaced when our scanner swept the npm ecosystem for packages with 1,000+ stars, no meaningful releases in 12+ months, and active weekly download traffic. rrule.js cleared all three filters, with one stand-out metric: it's the only mature JavaScript library that fully implements the RRULE spec.

The repo has 2,450 stars and 3,200+ monthly npm downloads. More importantly, it appears as a dependency in calendar integrations for major enterprise SaaS tools. Recurring event logic — "every other Tuesday at 3pm, except holidays" — is notoriously difficult to implement correctly. The iCalendar specification that governs recurring event rules is a 100+ page RFC. rrule.js implemented it. That's the moat.

Signal Breakdown: Why 73/100

Our scoring model evaluates each deal across five dimensions. Here's how rrule.js landed on each one:

The score reflects a real complexity tradeoff: the domain (iCalendar recurrence rules) is genuinely complex, and so is the codebase that implements it. A new owner needs JavaScript fluency and comfort reading RFC specifications. The flip side of that complexity: no competitor has bothered to build a better alternative. When something is hard to build and no one else has built it, the barrier to competition is the moat.

The Discovery Story: What Signals Flagged This Deal

Four signals converged when our scanner processed rrule.js:

RFC monopoly. Search npm for "rrule" and you find rrule.js — then a collection of wrappers, forks, and partial implementations built on top of it. There is no credible alternative that fully implements the iCalendar recurrence rule specification in JavaScript. This is a genuine monopoly signal: the space is occupied, competitors have tried, and the original library still wins by specification completeness.

Enterprise dependency depth. rrule.js appears in the package.json of calendar and scheduling tools used by enterprises. When enterprise teams build "recurring meeting" or "schedule weekly report" features, they reach for rrule.js. Enterprise dependencies are sticky in ways that consumer dependencies are not — switching requires testing against the RFC specification, which means whoever evaluates the migration understands immediately why they're not switching.

Scheduling SaaS as a category. Calendly, Cal.com, Savvycal, and a dozen smaller scheduling tools have made "scheduling as a service" a mainstream product category. Every scheduling SaaS that handles complex recurrence patterns needs RFC-compliant RRULE parsing. That's rrule.js's home turf. The category scaling has expanded the library's total addressable market without the library changing at all.

Open issue density with high-value requests. The GitHub issue tracker contains unresolved questions from engineering teams at identifiable companies. These aren't student projects hitting edge cases — they're engineering teams building production features asking for API improvements, TypeScript type refinements, and timezone handling edge cases. Each open issue is a proxy for a paying customer who'd upgrade to a hosted API version if one existed.

Acquisition Economics

At $4,300 and $140/month current MRR, the raw multiple is ~31x. The real value is in the hosted calendar API opportunity — which the library is perfectly positioned to anchor.

Metric	At Acquisition	12-Month Target
Monthly Recurring Revenue	~$140	$1,500–$2,800
Monthly npm Downloads	3,200+	4,000–5,500
Acquisition Cost	$4,300	—
API Build + Development Effort	—	~$4,000 (80 hrs)
Total Investment	—	~$8,300
Exit Potential (18–24 months)	—	$35,000–$55,000

The exit math assumes the Calendar API tier reaches $2,500 MRR at a conservative 15–18x multiple for a developer tool SaaS. Total ROI on $8,300 invested: 4–6x in 24 months. The scheduling market premium means developer tools with RFC-compliant implementations command higher multiples than average — schedule APIs sell for 20–25x MRR to acquirers in the calendar space.

Growth Levers: What a New Owner Does in Year One

Lever 1: Hosted Recurrence Rule API ($29–$99/mo)

The highest-value opportunity. A REST API that accepts an RRULE string and returns an array of occurrence dates — with timezone support, exclusion dates, count limits, and date-range filtering — is a productized version of exactly what developers are implementing manually today. The value prop: no npm dependency, no bundle bloat, no maintenance surface. $29/month for 10,000 API calls/month; $99/month for unlimited with priority support. Enterprise scheduling teams will pay this without negotiating.

Lever 2: TypeScript-First v3.0

The existing library was originally written in JavaScript and TypeScript types were added incrementally — the types are incomplete and the edge cases are undocumented. A v3.0 rewrite with TypeScript-first design, improved type inference for RRULE options, and comprehensive JSDoc would generate significant organic press in the TypeScript community. The "fully typed RFC-compliant RRULE library" announcement has HackerNews front-page potential. This is a marketing event disguised as a technical upgrade.

Lever 3: Integrate with Cal.com and Calendly Ecosystems

Both Cal.com (open source) and Calendly (enterprise SaaS) have developer ecosystems. A rrule.js integration guide, official SDK helpers for common scheduling patterns, and active presence in those communities' developer forums positions the library (and its hosted API) as the authoritative RRULE implementation for the scheduling category. Developer ecosystem positioning generates organic installs that compound.

Lever 4: Human-Readable RRULE Generation

One of the top feature requests in the issue queue: converting an RRULE string to a human-readable description ("Every other Tuesday at 3pm, except December 25th"). This is a genuinely useful feature that doesn't exist in any competing library. Adding it as a free feature generates buzz; offering an AI-enhanced version ("describe your schedule in plain English, get RRULE") as a $9/month add-on converts well to the developer audience already using the library.

Risk Factors

The Bottom Line

rrule.js is a buy abandoned npm package opportunity with a specific and defensible position: it's the only complete JavaScript implementation of a complex specification that the scheduling SaaS boom has made newly important. The $4,300 asking price buys a library with 3,200 monthly users, enterprise dependency depth, and an addressable market that's growing faster than the library ever has.

The $8,300 total investment against $35,000–$55,000 exit potential represents the highest-risk deal in this batch — the technical complexity is real — but also the highest ceiling. The scheduling API opportunity is a category that didn't meaningfully exist five years ago. rrule.js owns the only RFC-compliant seat at that table. That's the micro-acquisition deal flow insight that doesn't appear on traditional SaaS marketplaces: a library that became infrastructure for a market category it predates.