Skip to content
Moat or Bloat

epub-wasm

WASM library for parsing EPUB files into JSON structure

Library Rated 7 Oct 2026Dormant

Link
github.com/0xmiki/epub_wasm
Built by
will to code

Bloat

92/500

Where it landed on the scale

Bloat
0
Float
300
Moat
400

Summary

This is a small, single-purpose utility the builder made to scratch their own itch, published on GitHub and NPM. It likely works, but there's no sign of users, money, docs, or follow-through, and nothing has shipped in about nine months.

Bloat · Not much here works or looks likely to last, yet.

Breakdown

Five measures, 100 points each. Open the receipts under any of them to see the posts and pages behind the points.

Viability

Is there a real problem, someone who would pay, and a market this builder can actually reach?

EPUB parsing in the browser is a real annoyance, but this is a free developer utility with no pricing and no path to anyone paying. The builder describes it as something they made for their own use.

22/100

Rubric 21–40A real problem, but no plausible path to anyone paying, or a market well out of this builder's reach.

Receipts (2)

  1. The stated motivation is personal: frontend EPUB parsing libraries were a drag for the builder.

    “Dealing with all the epub parsing libraries on the frontend was a drag, so I made epub-wasm I give it epub, it gives me json structure I want Github | NPM”

    Post · @willtocode · 23 Dec 2025 · open on Telegram (opens in a new tab)

  2. The builder says it's about 800 lines of Rust and that they never want to look at the code again, which points to a personal tool rather than a product.

    “It's about 800 lines of code in rust. I could've implemented this with javascript... but it just didn't feel right to have chunky code on the frontend. With epub-wasm I never have to see it again, plus its much faster and I can run it anywhere I want. I truly never have to look at the code again 🤌”

    Post · @willtocode · 23 Dec 2025 · open on Telegram (opens in a new tab)

Moat

What stops someone copying it?

About 800 lines of Rust that wraps EPUB parsing is something another developer could rebuild in a weekend. There's no license, data, or distribution to protect it.

14/100

Rubric 0–20A thin wrapper or a clone that anyone here could rebuild in a weekend.

Receipts (2)

  1. The builder says the whole thing is about 800 lines of Rust, so it's small and easy to reproduce.

    “It's about 800 lines of code in rust. I could've implemented this with javascript... but it just didn't feel right to have chunky code on the frontend. With epub-wasm I never have to see it again, plus its much faster and I can run it anywhere I want. I truly never have to look at the code again 🤌”

    Post · @willtocode · 23 Dec 2025 · open on Telegram (opens in a new tab)

  2. The repo shows no license, no releases, and no homepage, so nothing sets it apart.

    Checked 7 Oct 2026 · github.com/0xmiki/epub_wasm (opens in a new tab)

Momentum

Did the updates keep coming?

It was worked on across two commit days (Dec 23 and Jan 6) and has had no update for about 274 days. That's a short burst, not steady shipping.

0/100

  • Sustained shipping0/60

    Worked on across 14 days.

  • Consistency0/40

    Updates in 1 of 1 month.

  • Quiet

    No update for 274 days, so scaled to 30%.

Receipts (2)

  1. Earliest post about it.

    “Dealing with all the epub parsing libraries on the frontend was a drag, so I made epub-wasm I give it epub, it gives me json structure I want Github | NPM”

    Post · @willtocode · 23 Dec 2025 · open on Telegram (opens in a new tab)

  2. Most recent post about it.

    “It's about 800 lines of code in rust. I could've implemented this with javascript... but it just didn't feel right to have chunky code on the frontend. With epub-wasm I never have to see it again, plus its much faster and I can run it anywhere I want. I truly never have to look at the code again 🤌”

    Post · @willtocode · 23 Dec 2025 · open on Telegram (opens in a new tab)

Infrastructure

Does a real, working product exist?

A working-sounding library is published on NPM and GitHub, and the repo is live. It has no releases, license, docs, or site, so how complete it is can't be confirmed.

53/100

  • It's live20/20

    https://github.com/0xmiki/epub_wasm responded when checked.

  • HTTPS5/5

    Hosted on a platform (store, GitHub or Telegram), so HTTPS is the platform's.

  • Real product25/35

    The library was published to NPM and GitHub and the builder says it takes an EPUB and returns JSON. That suggests it works, but there are no releases, docs, or demo here to show how complete it is.

  • Own home0/10

    No home found.

  • Maintained0/15

    Last sign of shipping 2026-01-06.

  • Operations3/15

    It's on two platforms (GitHub and NPM), but there's no backend, docs site, API reference, or status page.

Receipts (5)

  1. https://github.com/0xmiki/epub_wasm responded when checked.

    Checked 7 Oct 2026 · github.com/0xmiki/epub_wasm (opens in a new tab)

  2. The builder says they give it an EPUB and get the JSON structure they want, with links to NPM and GitHub.

    “Dealing with all the epub parsing libraries on the frontend was a drag, so I made epub-wasm I give it epub, it gives me json structure I want Github | NPM”

    Post · @willtocode · 23 Dec 2025 · open on Telegram (opens in a new tab)

  3. The repo is live and described as generating structured JSON from EPUB with WASM, but it has zero releases.

    Checked 7 Oct 2026 · github.com/0xmiki/epub_wasm (opens in a new tab)

  4. The posts link both a GitHub repo and an NPM package.

    “Dealing with all the epub parsing libraries on the frontend was a drag, so I made epub-wasm I give it epub, it gives me json structure I want Github | NPM”

    Post · @willtocode · 23 Dec 2025 · open on Telegram (opens in a new tab)

  5. The repo has no homepage and no releases.

    Checked 7 Oct 2026 · github.com/0xmiki/epub_wasm (opens in a new tab)

Sustainability

Is it being set up to last?

Nothing here supports it over time: no pricing, payments, license, privacy or terms pages, or support contact. The builder treats it as a finished personal tool, so there's no sign of ongoing commitment.

3/100

  • Distribution0/30

    No working way to get it was found.

  • Payments0/15

    No payment provider found.

  • Pricing0/10

    No pricing found on the site.

  • Revenue0/5

    Nothing in the posts or repo points to paying customers or any revenue.

  • Privacy policy0/7

    No privacy policy found.

  • Terms0/5

    No terms of service found.

  • Support0/8

    No support contact found.

  • Commitment3/20

    There was a short burst of work over two commit days, then nothing. The posts show no roadmap, team, community, or dedicated channel.

Receipts (3)

  1. The post describes a personal tool and mentions no customers or pricing.

    “Dealing with all the epub parsing libraries on the frontend was a drag, so I made epub-wasm I give it epub, it gives me json structure I want Github | NPM”

    Post · @willtocode · 23 Dec 2025 · open on Telegram (opens in a new tab)

  2. Commits happened only on 2025-12-23 and 2026-01-06, with no releases since.

    Checked 7 Oct 2026 · github.com/0xmiki/epub_wasm (opens in a new tab)

  3. The builder says they never want to look at the code again, which signals no plan to keep developing it.

    “It's about 800 lines of code in rust. I could've implemented this with javascript... but it just didn't feel right to have chunky code on the frontend. With epub-wasm I never have to see it again, plus its much faster and I can run it anywhere I want. I truly never have to look at the code again 🤌”

    Post · @willtocode · 23 Dec 2025 · open on Telegram (opens in a new tab)