mrkeyoor.comAsk

edwardkim/rhwptested 09 Oct 2026commit 1a76570

rhwp review

rhwp is worth evaluating when HWP/HWPX web editing, CLI conversion or MCP access matches your requirements.

  • Build 195 s
  • Tests failed
23 sto install
  • 241 packages
Dev Toolsevaluationupdated 26 Oct 2026
+12stars / 7d

rhwp is an independent open-source HWP/HWPX viewer and editor built with Rust and WebAssembly. Its README also documents CLI conversion, an embedded MCP server, and limited HML support. These capabilities are documented project features; our recorded run verified a source build, not document rendering or editing accuracy.

Verdict

rhwp is worth evaluating when HWP/HWPX web editing, CLI conversion or MCP access matches your requirements. In our October 9, 2026 run at commit 1a76570, the build succeeded in 195 seconds, but the test command stopped during compilation because a generated test file was missing. That result establishes neither a passing suite nor a document-processing failure. Before adoption, verify your chosen distribution path and compare representative documents using recorded fonts, application versions and export settings.

We ran it

Lab card: what happened when we ran rhwp
Lab card from our sandbox run
Screenshot of rhwp (github.com/edwardkim/rhwp)
github.com/edwardkim/rhwp
Install✓ · 23s241 packages
Build✓ · 195s
Tests✗ · 209sran, no count parsed
Repo41589 files~1,548,360 lines of source · 5619.7 MB · 24 CI workflows · Dockerfile · tests dir

Answers from our run

Does rhwp build from source?

Dependencies installed in 23 seconds (241 packages), and the build succeeded in 195 seconds. We cloned commit 1a76570 into a clean Debian container with 3 CPUs and no project-specific setup.

Do rhwp's tests pass?

No. The project's own test command exited unsuccessfully after 209 seconds, and its output did not expose an individual test count.

Who should not use rhwp?

Teams requiring demonstrated layout fidelity across their documents before adoption: our run did not measure document output.

What are the alternatives to rhwp?

hwp.js, pyhwp. rhwp is worth evaluating when HWP/HWPX web editing, CLI conversion or MCP access matches your requirements.

Setup3/5On October 9, 2026 at 1a76570, dependency download and build succeeded, but test compilation stopped on a missing generated file. The recorded source tree occupied 5,619.7 MB; installed-binary setup was not checked.
Docs4/5The supplied English README covers interfaces, setup and output limitations. It identifies the Korean roadmap as authoritative and describes Korean project records with English translations; documentation completeness was not exhaustively tested.
Community3/5The supplied issue history shows contributor investigation and maintainer integration of fixes. This supports visible participation, but does not measure adoption, response times or ongoing support capacity.
Maturity3/5The README documents several interfaces and the supplied history records completed renderer fixes. Our v0.8.7 source build passed, but test compilation and unmeasured document behavior limit the conclusion.

Who it’s for

Developers evaluating HWP/HWPX viewing or editing in a web application through @rhwp/editor or @rhwp/core.
Teams evaluating CLI document conversion or MCP access for Korean document workflows.
Contributors prepared to work with a large Rust repository and Korean project documentation, with English translations available.

Who it’s NOT for

Teams requiring demonstrated layout fidelity across their documents before adoption: our run did not measure document output.
Users expecting an official Hancom product: the project explicitly disclaims affiliation, sponsorship and endorsement.
Contributors requiring a verified passing test suite from this review: our recorded test command stopped during compilation because a generated test file was missing.
Teams relying on the distribution channels withdrawn in v0.8.4 without separately confirming current support.

Setup reality

In our recorded run on October 9, 2026, at commit 1a76570e833917d15817415a53c09ad61ab3203f, the dependency-download step succeeded in 23 seconds and the build step succeeded in 195 seconds. The record lists 241 dependencies. Download completion does not establish that the CLI was installed or checked as an installed binary.

The test command exited 101 after 209 seconds without timing out. Its tail reports that tests/generated/regression_suite_028.rs could not be read because it was missing, preventing compilation of that test target. The record provides no passing-test count and does not establish a runtime assertion failure or a broken document viewer.

The recorded repository measurements were 41,589 files, approximately 1,548,360 lines and 5,619.7 MB. The sandbox configuration was 3 CPUs, 12 GB memory and image lab-rust:1; that label does not establish the actual Rust version. The README specifies Rust 1.93.1 for source builds, Docker for WASM builds and Node.js 18+ for the web editor. Release binaries and npm packages are documented alternatives to building the whole source tree, but we did not install or exercise those distribution paths.

A source build is only the first adoption check

rhwp combines documented HWP/HWPX viewing and editing with CLI conversion and MCP access. Our recorded source build succeeded, but we did not measure whether it preserves your documents' layout. That distinction matters when choosing a tool for forms, tables or print output.

The English README describes a Rust and WebAssembly engine with HWP 5.0 and HWPX parsing, browser rendering, editing and export. HML support is narrower: the project limits it to corpus-verified HWPML 2.9/2.91 structures and describes preservation checks that block lossy saves involving unsupported content. These are project claims, not results from our sandbox.

Choose the interface that matches the job

The README documents @rhwp/editor for embedding the editor UI and @rhwp/core for direct WASM parser and renderer calls. It also describes native CLI release archives and an embedded MCP server for hosts such as Claude Code. MCP operations include document information, search, field filling and conversion; session tools support repeated queries and edits without reparsing.

Those interfaces give developers several integration options. Our run did not exercise the browser editor, npm packages, MCP sessions or document conversion, and it did not assess how an MCP host handles document data.

The v0.8.4 release is relevant distribution history. It retained native CLI releases, the two npm packages, GitHub Pages, editor marketplaces and Chrome, Edge and Firefox extensions. It withdrew channels unintentionally enabled in v0.8.3, including PyPI, @rhwp/node, the GHCR CLI image, operating-system packages and installation automation. Treat that as a dated release policy, rather than evidence that every historical installation route remains supported.

What our recorded run established

Our run was recorded on October 9, 2026 at commit 1a76570e833917d15817415a53c09ad61ab3203f, whose commit date is October 6, 2026. The build log identifies rhwp v0.8.7. This is a different scope from the historical v0.8.4 release discussion.

The dependency-download step completed successfully in 23 seconds. The record lists 241 dependencies; this is not an installed-binary check. The build step completed successfully in 195 seconds, including the compilation activity visible in its tail.

The test command exited 101 after 209 seconds and did not time out. The decisive error was a missing generated source file, tests/generated/regression_suite_028.rs, which prevented compilation of the regression_suite_028 test target. The available record does not explain why the file was missing or provide a passing-test total. It therefore supports a test-compilation obstacle in this checkout, not a conclusion that document viewing, editing or conversion is broken.

The repository measured 41,589 files, approximately 1,548,360 lines and 5,619.7 MB. The record detected 24 CI workflows, a Dockerfile, a Compose file and a tests directory. These are repository observations, not proof that those workflows or deployment paths passed. The sandbox configuration was 3 CPUs, 12 GB memory and image lab-rust:1. No new execution, document workload, installed-CLI check or security audit forms part of this review.

Check fidelity with a defined reference

The historical renderer reports should be read with their resolution status. Issue #6095 described a nested-table placement problem with roughly 303 pixels of excess space. It was closed as completed on August 26, 2026, with a maintainer reporting integration of the fix. It should not be presented as an unresolved defect in the measured October checkout. The upstream validation reported there is separate from our run.

A closed issue also does not establish fidelity for every document. For an adoption trial, choose representative files, record the reference application's version, fonts and export route, then compare page count, table continuation, text placement and saved output. The README itself cautions that Hancom PDF output varies by tool, version and output path. Define the reference environment before interpreting a difference.

How to read the scores

Scores are editorial judgments on a five-point scale: 1 means the supplied evidence shows a major obstacle; 2 means substantial constraints; 3 means a usable evaluation starting point with material unknowns; 4 means strong evidence for the stated scope with limited gaps; 5 requires broad corroboration. They are not benchmark results, adoption measurements or compatibility guarantees.

Setup receives 3 because dependency download and build succeeded, while test compilation stopped and the source tree was large. Documentation receives 4 for the supplied English feature and setup documentation, qualified by the Korean source-of-truth roadmap and Korean project records. Community receives 3 for visible contributor and maintainer participation in the supplied issue history; support responsiveness and adoption were not measured. Maturity receives 3 because the documented interfaces and resolved renderer work provide a basis for evaluation, while our run leaves runtime behavior and document fidelity unverified.

For a narrower requirement, hwp.js describes itself as a web HWP viewer and parser library. pyhwp documents HWP v5 stream analysis and extraction, with experimental OpenDocument and plain-text conversion. Neither alternative was run here. Choose based on the operation you need, then verify that operation with your files.

Alternatives

ProjectWhat it isPick it when
hwp.jsAn open-source HWP viewer and parser library powered by web technology.Evaluate it when your requirement is a web HWP viewer or parser library.
pyhwpAn HWP Document Format v5 parser and processor with stream extraction and experimental conversion.Evaluate it for HWP v5 stream analysis or extraction, or experimental conversion to OpenDocument or plain text in a Python workflow. Confirm compatibility with your Python environment separately.

What people are saying

  1. [github-trending] edwardkim/rhwp

Sources

  1. rhwp Korean README
  2. rhwp English README
  3. rhwp repository
  4. rhwp v0.8.4 release
  5. Nested-table pagination report #6095
  6. Table row pagination report #6035

More dev tools reviews