The devicons logo block has two sources and no fallback image, and one package has no docs
devicons - Crisp and clear logos & icons for developers.
At a glance
- What is it?
- devicons is a pnpm monorepo that generates a developer icon font and framework components from one core pipeline. What the repository documents is thin: a package table with a gap in it, a logo element that cannot render on its own, and a contributing link that leaves the site, while the scripts reveal a seventh package the table never lists.
- Who is it for?
- devicons fits a project that wants consistent developer icons across a site and its components without drawing them, and the generated framework packages mean you should take the font package or a generated package rather than editing components by hand.
- 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 33 days ago.
- What is it written in?
- Mainly MDX, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- vorillaz/devicons2,799 ★ · +22
| Repository | 2026-09-28 | 2026-11-15 |
|---|---|---|
| vorillaz/devicons | 2.8k | 2.8k |
22 Stars in the last 48 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The logo element carries two sources and no image
The header of the file is raw HTML rather than Markdown, and the part that draws the wordmark is a picture element wrapped in an anchor. Inside it sit two source elements, one for dark colour schemes and one for light, and after them there is no img element. A picture with only sources and no fallback image has nothing to display in a renderer that ignores the media queries, and many Markdown pipelines strip source elements outright, which leaves an empty box. Both sources point at raw.githubusercontent.com under the canary branch rather than the default one, so the README that ships with a tagged release still advertises assets from an unreleased branch. The homepage link beside the documentation link is plain http while every asset URL in the file is https.
Six packages, five documentation pages and one unscoped name
The package table is the whole of the feature documentation. The devicons package is described as an icon font, CSS and SVG sprite, and is the only entry without a scope: it is plain devicons, while the other five are @dev.icons/react, @dev.icons/vue, @dev.icons/svelte, @dev.icons/core and @dev.icons/figma. Inside that scope the naming is consistent; the font package is the outlier, and an unscoped name on a public registry is the one identifier here that cannot be namespaced later. The Figma plugin is also the only row whose documentation column holds a dash rather than a link, so five of the six packages have a page on the documentation site and the plugin does not.
The framework packages are generated from core, not written by hand
The manifest shows how the pieces relate. The build script delegates to @dev.icons/core, and three separate generate scripts exist, one each for React, Vue and Svelte, which means the component packages are output rather than source. The build variants prove it by turning parts of core off: build:icons passes --no-frameworks --no-font-pkg, while build:frameworks passes --no-font --no-sprite --no-font-pkg. Four switches are in play across those two commands, so core can emit any combination of framework components, the font package, the font itself and the sprite. The consequence for a consumer is practical: a fix belongs in core or in the source data, and a hand edit inside a generated component package will be overwritten by the next generate run.
A seventh package is built by the scripts and missing from the table
The build scripts reference a workspace package that the table never lists. build:website delegates to @dev.icons/website, which appears in neither the package table nor the surrounding prose. The file gives its location away indirectly, because the logo sources point at apps/website/public/brand/, so the site itself is a workspace package with a build step of its own. That makes seven workspaces behind a six-row table. The repository layout matches the rest of the story: an apps/ directory, a packages/ directory, a scripts/ directory, and an examples/ directory containing core, font, react, svelte and vue, five subdirectories for the five documented packages and none for the Figma plugin.
The root manifest is private, versioned 0.0.0 and has no keywords
The workspace root is named @dev.icons/repo, marked private, and carries version 0.0.0, which is the conventional placeholder for a private root rather than a shipped version. It declares [email protected] as its package manager and repeats the one-line description. Its keywords field is an empty array, so the package that describes the whole project publishes none, while the description line does the work instead. Two more details place the repository in a specific toolchain: a pnpm-workspace.yaml and a pnpm-lock.yaml at the root, and a vitest.workspace.ts for the test runner, with the test script running every package's tests in parallel through a recursive call.
Three releases on one afternoon, then nothing for months
The three most recent releases all carry the date 2026-04-19. v1.0.0-canary.1 went out at 18:34, v1.1.0-canary.1 at 22:07, and v1.1.0 itself at 22:19, so the final tag landed twelve minutes after its own canary. The canary naming is explained by the tooling: the root devDependencies are dominated by semantic-release with its changelog, commit analyzer, git, github and release notes generator plugins, plus the monorepo variant and conventional-changelog-conventionalcommits, which is the standard way to publish prereleases from a multi-package tree. The last recorded push to the default branch is 2026-05-10, three weeks after that release and about five months before 2026-10-04. One further inconsistency in that list: vitest is pinned to the exact version 3.1.3 while every other devDependency uses a caret range.
Contributing and installing both leave the repository
Neither of the two things a newcomer needs is in the file. Getting started points at an installation guide and a quick start, both hosted on the documentation site, and no install command appears anywhere in the text. Contributing points at a page on the same site rather than at a file in the tree, and the top-level listing confirms why: there is no contributing file next to the README, the changelog or the licence. What the root does carry is tooling configuration, with .npmrc, .prettierrc and .prettierignore, and a CHANGELOG.md. So the repository is where the pipeline lives and the documentation site is where the instructions live, and a reader who only clones the repository gets neither.
Editorial conclusion
devicons fits a project that wants consistent developer icons across a site and its components without drawing them, and the generated framework packages mean you should take the font package or a generated package rather than editing components by hand. Before adopting it, check that the Figma plugin has no documentation page of its own, plan for the fact that the only install instruction lives off-site, and pin the exact version you build against, since the published 1.1.0 has been out since April while the default branch has moved since.
Frequently asked questions
how to install devicons
The README gives no command. It points at an installation guide and a quick start on the documentation site, and the packages it would install are the unscoped devicons font package or one of @dev.icons/react, @dev.icons/vue and @dev.icons/svelte.
Which devicons packages are published?
Six are named: devicons for the icon font, CSS and SVG sprite, @dev.icons/react, @dev.icons/vue and @dev.icons/svelte for components, @dev.icons/core for the build pipeline, and @dev.icons/figma for the Figma plugin.
Are the devicons framework components edited by hand?
They are generated. The root manifest has generate:react, generate:vue and generate:svelte scripts, and the build variants turn parts of @dev.icons/core off with flags like --no-frameworks and --no-font, so changes belong in core or the source data rather than in a generated package.
Is there documentation for the devicons Figma plugin?
No. It is the only row of the package table whose documentation column holds a dash instead of a link, and the examples directory covers core, font, react, svelte and vue without one for the plugin.
What license is devicons released under?
MIT, with a LICENSE file in the repository root alongside a CHANGELOG.md. The workspace root manifest itself is marked private and carries the placeholder version 0.0.0.
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.
[](https://hysenlabs.com/projects/vorillaz-devicons)Star history chart for your README
[](https://hysenlabs.com/projects/vorillaz-devicons)Was this useful?