What it does
Galaxy is the open-source backing store for Uiverse.io — a community-driven UI component platform. Every element submitted and approved on the platform gets automatically committed here: 3,571 HTML files spanning 11 categories, each one a self-contained snippet you can copy straight into any project.
Why I starred it
The pitch is simple: you need a brutalist input field, a pulsing loader, a toggle switch with a satisfying click feel. You could spend 40 minutes writing CSS from scratch, or you can pull something from Galaxy. The collection has grown to a point where most standard UI patterns exist in several creative variants.
What made me look closer was the naming convention. Files are formatted as username_adjective-animal-number.html. You get things like 0xnihilism_brown-puma-30.html and Creatlydev_grumpy-crab-66.html. It sounds trivial, but the username prefix means attribution is baked into the filename — you always know who made it. The platform generates these slugs automatically, and they carry through to the commit message: "Launching a new button to space! 🚀 - https://uiverse.io/Creatlydev/grumpy-crab-66". The whole pipeline — submit, review, commit — is automated.
The last git commit is from September 2024. The repo had active daily commits throughout 2023 and most of 2024, then went quiet. That gap is worth noting if you are evaluating it as a living collection versus a snapshot.
How it works
The repo structure is completely flat: 11 directories, one per category, each containing individual HTML files. No build step, no package.json, no framework dependencies. The categories and their component counts:
| Category | Count | |---|---| | Buttons | 1,000 | | Cards | 726 | | loaders | 718 | | Toggle-switches | 260 | | Inputs | 226 | | Forms | 180 | | Checkboxes | 171 | | Patterns | 103 | | Radio-buttons | 102 | | Tooltips | 62 | | Notifications | 23 |
Each file is a standalone HTML snippet with an embedded <style> block or Tailwind classes in the markup, depending on the contributor's approach. The comment at the top carries metadata:
<!-- From Uiverse.io by 0x3ther - Tags: simple, button, social media, hover button, tailwind, tailwindcss -->
<div class="flex items-center justify-center h-full">
<button
class="text-white bg-gradient-to-r from-blue-500 via-blue-600 to-blue-700
hover:bg-gradient-to-br focus:ring-4 focus:outline-none
focus:ring-blue-300 dark:focus:ring-blue-800 shadow-lg
shadow-blue-500/50 font-medium rounded-lg text-sm px-5 py-2.5"
type="button"
>
Facebook
</button>
</div>Contrast that with a CSS-first entry from the same Buttons directory:
/* From Uiverse.io by 0x-Sarthak - Tags: button, hover, rounded, animated, hover button */
.cta {
position: relative;
padding: 11.5px 18px;
transition: all 0.2s ease;
border: 3px solid #552da8;
border-radius: 50px;
background: #552da8;
}
.cta:before {
content: "";
position: absolute;
border-radius: 50px;
background: white;
width: 45px;
height: 45px;
transition: all 0.8s ease;
}
.cta:hover:before {
width: 100%;
background: #1c1c1c;
}No abstraction layer, no component model, no props. The CSS animations and keyframes are self-contained. You paste the HTML, paste the CSS, done. That simplicity is a deliberate constraint: Uiverse.io enforces single-file HTML submissions, which is why the whole archive can be stored as flat files and browsed without a build tool.
The loaders directory has some of the more elaborate entries. 0xnihilism_brown-puma-30.html in the loaders category is tagged "brutalism, orwellian" and renders a surveillance-camera-inspired spinner with a scanning pupil, eyelid animations, and scanlines — all in under 100 lines of CSS keyframes. The tags in the comment header are not just decorative; they feed the Uiverse.io search index, which is the intended way to browse the collection.
There is no scripting in the pipeline. The Uiverse.io platform handles review and CI. Each approved submission triggers an automated commit with that emoji-laden message format. The repo itself has no GitHub Actions, no workflows, no tooling at all — it is a pure content archive.
Using it
Browsing works best on uiverse.io with its visual preview grid. But if you want to pull components programmatically or grep across the collection:
git clone https://github.com/uiverse-io/galaxy
cd galaxy
# Find all brutalist-tagged components
grep -rl "brutalist" . --include="*.html"
# Count Tailwind vs CSS components in Buttons
grep -l "tailwind" Buttons/*.html | wc -l # Tailwind
grep -L "tailwind" Buttons/*.html | wc -l # Pure CSS
# Pull a specific component's source
cat Buttons/0x-Sarthak_hungry-penguin-30.html
For direct integration into a project, drop the HTML into your template and either include Tailwind (if the snippet uses it) or paste the <style> block. There is no npm install, no peer dependencies.
Rough edges
The Tailwind/CSS split is inconsistent with no way to filter from within the repo — you have to grep or rely on the comment tags. Some files tag themselves as Tailwind but use a mix of both, because contributors sometimes start with Tailwind and add custom CSS for the animation parts Tailwind does not cover cleanly.
The last commit was September 2024. The platform is still active — Uiverse.io shows recent submissions — but they stopped syncing to this repo. That means you are getting a large but aging snapshot rather than a live mirror. If the platform itself is your source of truth, you do not need this repo. If you want a local, greppable, version-controlled copy of the collection, be aware it is frozen at roughly 3,500 elements.
No tests, no linter, no validation that submitted HTML is well-formed. A handful of files have minor HTML issues that only matter if you are parsing the collection programmatically. And because PR contributions are disabled (by design — everything flows through the platform), there is no community-maintained quality pass on the raw files.
Bottom line
Galaxy is the right tool if you need a local, copy-pasteable library of CSS/Tailwind UI components and want to avoid the visual platform. For everyday use, just browse Uiverse.io directly — but knowing the raw files are here and greppable is genuinely useful.