HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dotnet
Open-XML-SDK
C#2014–2026
dotnet / Open-XML-SDK

Open-XML-SDK

Open XML SDK by Microsoft

11Distinct people
12Mentions
0Explicit recommenders
4.6KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open XML SDK by Microsoft

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year12 dated mentions

Observed mentions: 2014-06-26 17:38:31 UTC to 2026-10-12 02:14:38 UTC.

012342014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC413
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC303

What Hacker News says

12 sources
I doubt Microsoft will take it seriously enough now, when it's in such an early state. What matters here is if this `wordcraft` app gets serious widespread use and businesses (which is Microsoft's main revenue source) start using this in favour of MS Word. Then I'd say anything's possible and testing in court whether LLM-vibecoded reverse engineered-apps actually do infringe on IP-rights is something Microsoft would be willing to risk to protect their greater Office 365 subscription revenue. This is one of those actual slipery slope scenarios - first Word, then Powerpoint, then Excel, then maybe even the more niche apps like Visio, or Access or Project. As it's reverse engineered, I wonder if copyrights even apply? It's likely Microsoft would assert its patent rights. But firstly why would a business that depends on Word to the point they
Read the rest
pay Microsoft for it,want to even move to a vibe-coded alternative anyway? The support you get from Microsoft is very different from an open source app, to the point many Word users wouldn't even know what Github is, let alone even know how to raise an issue there to get help. The 'threat' this wordcraft project poses, I think is very minimal even in the long run, to Microsoft. But side note: why even bother reverse engineering Word? The file format is very well specified - I think I've used at least 4 Word alternatives, and once wrote a basic C# app that could read and render most docx files, using the official Office Open XML SDK (https://github.com/dotnet/Open-XML-SDK). There's tons of documentation on how to parse DOCX files, so of all the apps to reverse engineer this seems to be the most redundant one. Why bother recreating Word? Why not just build a better writing app that just so happens to save its data to docx? Indeed, they probably started with Word because it was probably the easiest to verify considering many other, independent implementations of the DOCX file format exist. This whole effort seems very 'unthinking' - it's seems to be more of a 'because I can!' type of project rather than a genuine effort to improve the state of things with old-school word processing, which is one of those silently-operating-in-the-background type of jobs that is still very prevalent in a lot of industries, like the legal sector. I would love to get multiple typing cursors in Word, similar to VSCode and the Ctrl+Alt+Up/Down arrow shortcut, but then if Word doesn't already have it, then this project won't implement it either because it's a mindless, carbon copy. Why bother being just a follower? Why not start adding features Word doesn't have? As someone who has to deal with 1. users of Word and 2. the outputs of Word a lot I don't see this going anywhere unless it starts actually innovating.
In Ask HN: Will Microsoft sue vibe coded wordcraft for copying its Word GUI?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.