Jun Kim, oMLX Creator and Maintainer, Joins Hugging Face to Support MLX Community

On September 22, 2026, Hugging Face's official blog published an announcement confirming that oMLX creator and maintainer Jun Kim joined Hugging Face as a team member. Hugging Face said in the post that it was "very excited to welcome Jun to the team," and stated that the company is "fully committed to local AI, and MLX is a core part of the ecosystem." This is the only core fact directly confirmed by a first party in this incident.

The announcement also set out arrangements for the oMLX project itself: oMLX continues to use the Apache 2.0 license, and Jun Kim still leads the project as before. Hugging Face described this change as oMLX being upgraded from a side project to a project with full maintenance and funding support, arguing that this will bring stability and is expected to accelerate development. It is necessary to distinguish that the license and leadership arrangements are officially confirmed commitments, while "improved stability" and "accelerated development" are Hugging Face's own expectations and claims; the announcement gave no verifiable quantitative basis.

The announcement did not disclose oMLX's user scale, download counts, or performance benchmarks, nor did it explain Jun Kim's specific position, team affiliation, or funding arrangement details after joining. This means outsiders can currently only confirm that "the person joined, and the project's ownership and license remain unchanged," while being unable to assess the actual resource investment in this integration.

To understand the intent of this personnel change, one must first look at MLX's place in Hugging Face's narrative. The announcement said MLX is Apple's framework for local AI, specifically optimized for Apple Silicon; Hugging Face described itself as having been an MLX supporter since Awni and Angelos sent this "Christmas gift" in 2023, and said it takes pride in the Hugging Face Hub being the place where people find MLX models and contribute their own.

Under this framework, Hugging Face's expectation for oMLX is that it becomes a testbed for new ideas, while leveraging the foundational work such as mlx-lm and mlx-vlm that it already depends on. The announcement also mentioned one specific priority direction: accelerating the conversion from transformers model definitions to reference MLX implementations that can be consumed by different engines, so that each engine can focus on its own unique features.

Hugging Face also said it has already collaborated with multiple projects including mlx-lm, mlx-vlm, and LMStudio, and hopes to strengthen relationships with Cheng, Prince, Yagil, and their teams. These statements are all Hugging Face's plans and expectations; the announcement gave no timeline or evidence of progress, so they cannot be regarded as ecosystem integration that has already landed.

Shortly after the announcement was published, a branch outside the official narrative emerged. Jun Kim himself wrote in the blog comments that his GitHub account was "suspended" after the announcement, that it was most likely an automated false positive, and that he was contacting GitHub through multiple channels and hoped to resolve it as soon as possible. This comment itself received 7 🤯 reactions, indicating that the community's attention to this sudden situation was not low.

Judging from the timestamps of the announcement and the comment, the GitHub account suspension occurred shortly after the announcement was published, indicating that the incident was closely adjacent in time to this personnel announcement. But it must be made clear: whether the suspension was indeed an automated false positive and when it can be restored currently have no official conclusion; the announcement also did not provide an official reason for the GitHub account suspension or a restoration time.

This episode is worth discussing separately because it places the announcement's promise of "stability" in an awkward contrast: Hugging Face had just announced that oMLX would receive fuller maintenance and funding support, while the project maintainer's primary code-hosting account became unavailable within the same time window.

Beyond Jun Kim's comment, community comments provided more claims about oMLX's project accessibility. One community comment said oMLX's GitHub repository appeared to have been deleted and asked for the new address; another community comment said GitHub had been restored, but the releases page showed as empty; another community comment said a dmg installer needed to be given to a friend, but it could not be obtained that day.

These claims must be treated cautiously. They all come from the blog comments section and are community observations, not confirmed by GitHub or Hugging Face as a first party. Whether oMLX's GitHub repository was deleted, temporarily invisible, or migrated is described inconsistently in the sources; whether the empty releases page is a knock-on effect of the account suspension or an independent problem also cannot be judged from the available sources.

Only one point can be confirmed: on the day the announcement was published, multiple mutually corroborating community reports appeared around oMLX's accessibility, pointing to a service disruption within the same time window. As for the scope and cause of the disruption, the available evidence is insufficient to reach a conclusion.

Putting the above facts together, one can see an inference more worthy of attention than the personnel change: oMLX, as a project on which Hugging Face pins "testbed" expectations, relies heavily on a single GitHub account for code hosting, release distribution, and installer acquisition. When that account was suspended, the repository, the releases page, and dmg acquisition were almost simultaneously affected.

It should be noted that this causal chain is an inference based on the sources, not a proven fact. The sources did not confirm a direct causal relationship between the repository deletion, the empty releases page, and the account suspension, nor did they explain whether mirrors or backup distribution channels exist. But even taking only the literal content of the community reports, the result that users could not obtain the dmg installer on the day of the announcement is already enough to show the degree to which the distribution chain depends on a single platform.

This also explains why the "stability" wording in Hugging Face's announcement needs to be treated as an expectation rather than a conclusion: true stability depends not only on whether the maintainer receives funding and full-time commitment, but also on whether the external platforms and account systems the project relies on have redundancy.

First, the official reason for the GitHub account suspension and the restoration time. Currently there is only Jun Kim's own statement, namely that it was most likely an automated false positive and that he is contacting GitHub through multiple channels; until GitHub or Hugging Face provides an explanation, the nature of this incident remains uncertain.

Second, the final status of the oMLX repository and releases page. Community reports said the repository appeared to have been deleted and the releases page was empty, but these claims have not been confirmed by a first party; whether the repository was deleted, temporarily invisible, or migrated needs to be based on follow-up information from official channels.

Third, whether the "full maintenance and funding support" promised by Hugging Face can translate into observable results. The announcement said this will bring stability and is expected to accelerate development, and also proposed directions such as oMLX as a testbed, strengthening collaboration with projects including mlx-lm, mlx-vlm, and LMStudio, and simplifying the conversion from transformers to reference MLX implementations, but it gave no timeline or evidence of progress. Whether these expectations are fulfilled remains to be seen.