HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
eclipse-openvsx
openvsx
Java2020–2026
eclipse-openvsx / openvsx

openvsx

An open-source registry for VS Code extensions

9Distinct people
12Mentions
0Explicit recommenders
2.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An open-source registry for VS Code extensions

GitHub

Where it is used

No documented product use has been verified yet.

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:56:55 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: 2020-03-31 19:59:46 UTC to 2026-10-30 19:33:38 UTC.

01232020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 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): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 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
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC321
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 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

2 sources
The claims of AI use were unsubstantiated and pure conjecture, which was pointed out by people who understand language, including me. Now it appears that the community has used an MIT attribution violation to make the Zigbook author a victim of DMCA abuse. That doesn't look great to me. It doesn't look like a community I would encourage others to participate in. > tried to claim a namespace on open-vsx It seems reasonable for the zigbook namespace to belong to the zigbook author. That's generally how the namespaces work right? https://github.com/search?q=repo%3Aeclipse%2Fopenvsx+namespa... https://github.com/eclipse/openvsx/wiki/Namespace-Access. IMO, this up there with the "but they were interested in crypto!" argument. The zigbook author was doing normal software engineer stuff, but somehow the community tries to twist it into something
Read the rest
nefarious. The nefariousness is never stated because it's obviously absurd, but there's the clear attempt to imply wrongdoing. Unfortunately that just makes the community look as if they're trying hard to prosecute an innocent person in the court of public opinion. > At a certain point, that starts to look outright malicious. Malicious means "having the nature of or resulting from malice; deliberately harmful; spiteful". The Zig community looks malicious in this instance to me. Like you, I don't have complete information. But from the information I have the community response looked malicious, punitive, harassing and arguably defamatory. I don't think I've ever seen anything like it in any open source community. Again, prior to the MIT attribution claim there was no evidence the author of Zigbook had done anything at all wrong. Among other things, there was no evidence they had lied about the use of AI. Malicious and erroneous accusations of AI use happen frequently these days, including here on HN. Judging by the strength of the reaction, the flimsiness of the claims and the willingness to abuse legal force against the zigbook author, my hunch is that there is some other reason zigbook was controversial that isn't yet publicly known. Given the timing it possibly has to do with Anthropic's acquisition of Bun.
In Zig quits GitHub, says Microsoft's AI obsession has ruined the service
For context, Open VSX is run by the Eclipse foundation, which also develops the Eclipse Theia editor, which is basically a clone of VS Code (not a fork, like VS Codium). The Open VSX registry is open source (https://github.com/eclipse/openvsx) and self-hostable, although I have no experience with that. I assume it's possible to host your own instance with the extensions you want instead of relying on the free public instance. Personally I'm more of a Sublime guy, but people looking for an open VSC alternative should consider Theia over VSC forks. It seems like the smarter long term investment if you want to get out from Microsoft's control.
In OpenVSX, which VSCode forks rely on for extensions, down for 24 hours

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.