reicon publishes an open source SVG icon set through a dozen framework packages and a docs site hosted on Vercel. Reading its package table, root manifest and credit line closely shows an empty version column, a build chain that never validates the icons, and a second license sitting underneath the MIT declaration.

Can I use dqev/reicon commercially?

Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.

Is dqev/reicon still maintained?

Yes. The repository last received commits 3 days ago.

What programming language is dqev/reicon written in?

Mainly HTML, according to GitHub's language statistics.

reicon: 12 packages, two licenses, an empty table

At a glance

What is it?: reicon publishes an open source SVG icon set through a dozen framework packages and a docs site hosted on Vercel. Reading its package table, root manifest and credit line closely shows an empty version column, a build chain that never validates the icons, and a second license sitting underneath the MIT declaration.
Who is it for?: reicon suits a team that wants one icon set with the same names across React, Vue, Svelte, Angular, Astro, Flutter and a handful of editors, and taking the packages straight from npm avoids depending on the docs site at all. Before you commit, settle the licensing question for the icon files themselves, because the root MIT declaration sits next to a credit line naming CC BY 4.0 material and one source with no license named.
Can I use it commercially?: Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?: Yes. The repository last received commits 3 days ago.
What is it written in?: Mainly HTML, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on October 3, 2026, and from our analysis. They are not legal advice.

Editorial analysis

Written by the Hysen Labs editorial pipeline with AI assistance. Checked against the repository by machine, not yet reviewed by a named editor. How we write these Last updated September 18, 2026.

The root manifest is the docs site and it reads 1.4.1

The `package.json` at the repository root is not the icon library's manifest. It is named `reicon-docs`, marked `private`, set to `type: module`, and carries two workspaces, `apps/*` and `packages/*`. Because it is private, nothing publishes from the root. The script list inside it is what tells you how the project is actually arranged: nine of its entries are per package builds, each pointing at a script of the form `packages/<name>/scripts/build.cjs`, and the rest drive the documentation site under `apps/web`. The version field is the part that will confuse you. It reads 1.4.1, while the newest release is v1.5.0 published 2026-09-05, with v1.2.0 on 2026-08-04 and v1.1.1 on 2026-07-16 behind it. So the manifest at the root of the repository sits one minor version below its own newest tag, and nothing in the tree says whether that is deliberate, because the library packages are versioned separately from this file.

The package table has two columns that are empty in every row

Twelve packages are listed, and the Version and Downloads columns are blank for all twelve. What the table does carry is the distribution channel, and those differ per row: npm for `reicon`, `reicon-react`, `reicon-angular`, `reicon-react-native`, `reicon-vue`, `reicon-svelte`, `reicon-astro` and `reicon-mcp`, pub.dev for `reicon-flutter`, a Figma community plugin for `reicon-figma`, and the Visual Studio marketplace for `reicon-vscode`. `reicon-compose` has no registry link at all, only a docs link and a source path. That matters for the claim on the same page that the library is free for every framework you build with, since two of the twelve are not npm packages and one is not published anywhere the table names. The logo cells are mostly empty too, with one exception: the Astro row carries a `picture` element whose dark mode source points at `apps/web/public/framework-logos/astro.svg`. The one framework logo that renders is served out of the documentation app's own public directory, from a path inside the web app rather than from a shared asset package.

Nine node scripts run before vite, and none of them validate icons

The build is a chain rather than a single command:

code

node packages/reicon-react/scripts/build.cjs && node scripts/generate-website-search-index.mjs && node scripts/sync-icon-names.mjs && node scripts/seo/update-helmets.mjs && node scripts/generate-sitemap.mjs && node scripts/generate-llm-assets.mjs && vite build apps/web && node scripts/prerender-meta.mjs

Read the names in order and the shape of this project becomes clear: one package build, then a search index, an icon name sync, security headers, a sitemap, a generator for LLM assets, the docs site itself, and finally meta prerendering. Most of the chain exists so the documentation site is discoverable, not so the icons are packaged. A `postbuild` hook fires `node scripts/seo/ping.mjs` when the chain finishes. What is absent from the chain matters as much: a `validate:icons` script is defined alongside it and never invoked, so `node scripts/validate-icons.mjs` is something you run yourself. Icon validation does not gate this build. The same applies to `seo:check`, which points at `node scripts/seo/test.mjs` and is likewise outside the chain.

build:full only calls build, and the CDN file is minified elsewhere

Two entries in the same script table quietly undercut the impression of one pipeline. `build:full` is set to `npm run build`, so it is an alias for the same chain rather than a fuller one, and the name suggests a distinction the file does not make. The CDN artifact is built outside that chain as well:

code

npx terser packages/reicon/dist/cdn/reicon.js --compress --mangle -o packages/reicon/dist/cdn/reicon.js

That script takes a file already sitting at `packages/reicon/dist/cdn/reicon.js` and rewrites it in place. Producing that file is the job of `packages/reicon/scripts/build.cjs`, reachable on its own through `build:js`, and the default build chain never calls it: the only per package build inside the chain is the React one. So the compressed CDN file depends on a build step outside the chain that produces it, and on a second step that minifies the result. Of the nine `build:*` entries, each targeting its own `build.cjs`, exactly one is wired into the default build. The rest are separate commands, which is workable and worth knowing before you assume a clone plus one build command produces every published artifact.

MIT at the root, CC BY 4.0 in the credit line

The license section states that reicon is free for commercial and personal use and that the software is licensed under the MIT License, which matches the `LICENSE` file at the root and the MIT badge near the top of the page. The credits section says something different about the artwork. Reicon base icons are built using elements from Solar Icons, designed by 480 Design and named as CC BY 4.0, plus elements from Zappicon, for which no license is stated anywhere in the repository. Two licenses therefore sit in the same file describing the same icons, and the page does not say which of them covers the icon files and which covers the code. The MIT declaration covers this software; the credit line says the base icons are built from material under a different, attribution carrying license, and one of the two sources has no license attached at all. That is a question for the project rather than something to resolve by picking one. If you are shipping these icons, the attribution requirement is the part to check first, since both named licenses ask for it.

Two icon counts and three release titles that disagree

The headline on the landing section of the README says 2,700+ UI SVG icons. The release titles say something else. v1.1.1, published 2026-07-16, is titled Cleaned icon database. v1.2.0, published 2026-08-04, is titled 71,000+ Free SVG Illustrations Library. v1.5.0, published 2026-09-05, is titled Pure SVG Icon Library Focus. Read in order, those titles describe a scope that widened to illustrations and then narrowed back to icons, and the README quotes only the smaller current figure. The word illustrations in the middle title does not match the word icons used everywhere else, and no file in the repository tree reconciles the two numbers. The count is also the number most likely to be repeated in a project README or a dependency discussion, so it is worth knowing which figure the project itself currently stands behind. The last push to the repository is dated 2026-09-30, and the releases stopped on 2026-09-05, so the branch has moved since the newest tag without a matching release title to describe what changed.

The README carries no install command at all

The page runs to 288 words and contains no code sample, no install line and no usage example. What it does contain is the package table, the license statement, the credits, a sponsor acknowledgement for Vercel, and a pointer to the contribution guidelines in `CONTRIBUTING.md`. Anyone wanting the icons has to leave the repository and follow one of the registry links in that table. The repository tree gives the rest of the picture: a `data/` directory that holds the icon database, `scripts/validate-icons.mjs` and `scripts/sync-icon-names.mjs` for checking and syncing names, `docs/` for the documentation sources, and `apps/web` for the site that serves them. Hosting is Vercel, which the sponsor line credits for supporting the project and hosting it, and `vercel.json` and `.vercelignore` sit in the root for it. There is also a `SECURITY.md`, a `CODE_OF_CONDUCT.md`, a `CHANGELOG.md` and an `.agents/` directory. The absence of an install snippet is not a gap in the tooling, it is just a README that points outward.

Editorial conclusion

reicon suits a team that wants one icon set with the same names across React, Vue, Svelte, Angular, Astro, Flutter and a handful of editors, and taking the packages straight from npm avoids depending on the docs site at all. Before you commit, settle the licensing question for the icon files themselves, because the root MIT declaration sits next to a credit line naming CC BY 4.0 material and one source with no license named. Check the count you are quoting, since the release titles and the README headline disagree about whether this is a 2,700 icon set or a 71,000 item library. Run the icon validation yourself, since the default build never calls it, and note that the version in the root manifest is behind the newest tag.

Frequently asked questions

Is reicon free for commercial use?

The license section states reicon is free for commercial and personal use under the MIT License. The credits section adds that the base icons are built using elements from Solar Icons by 480 Design, named as CC BY 4.0, and from Zappicon, for which no license is stated. The page does not say which license covers the icon files themselves.

Which frameworks have a reicon package?

Twelve are listed: reicon, reicon-react, reicon-angular, reicon-react-native, reicon-vue, reicon-svelte, reicon-astro, reicon-flutter, reicon-compose, reicon-mcp, reicon-figma and reicon-vscode. Flutter ships through pub.dev, Figma through a community plugin and VS Code through the marketplace, and the compose row has no registry link in the table.

How many icons does reicon have?

The README headline says 2,700+ UI SVG icons. The release title for v1.2.0, published 2026-08-04, says 71,000+ free SVG illustrations, and v1.5.0, published 2026-09-05, is titled Pure SVG Icon Library Focus. No file in the repository reconciles the two counts.

How do I install the reicon React Native or MCP package?

Both are listed as npm packages, reicon-react-native and reicon-mcp, each with a docs page under reicon.dev/docs and a source path under packages/. The package table leaves its Version and Downloads columns empty in every row, so the published version numbers are not recorded there.

Does the reicon build check the icons before publishing?

Not in the default chain. A validate:icons script exists and runs node scripts/validate-icons.mjs, but the build script never calls it, so validation is a manual step. The chain does run a search index generator, an icon name sync, a sitemap generator, a helmet update, an LLM asset generator and a meta prerender step.

Official sources

Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

markdown

[![Hysen Labs](https://hysenlabs.com/badge/dqev-reicon.svg)](https://hysenlabs.com/projects/dqev-reicon)