Library / SDK
pheralb/svgl avatar
pheralb/svgl

Version 5.4.3 against a v5.0.0 tag, a link checker with a leading space, and an image that ships the builder's node_modules

🧩 A beautiful library with SVG logos. Built with Sveltekit & Tailwind CSS.

6,422 stars894 forksTypeScriptMIT

At a glance

What is it?
svgl is a SvelteKit site that collects SVG logos and hands them to a site, a set of utility scripts and a dozen community extensions. Its manifest is marked private, its site URL carries a Figma query parameter, and its Dockerfile runs a size check before the build it is meant to produce.
Who is it for?
Use the site and the API rather than the package, because the manifest is marked private and nothing in it publishes anything. If you want to run the thing yourself, the Dockerfile is the shortest path and it is stricter than it looks: check:size runs before the production build, so a size budget change breaks the image rather than a warning appearing in a log.
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 9 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

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

From daily snapshots

Star history

  • pheralb/svgl6,422 ★ · +88
Star history
Repository2026-09-232026-11-21
pheralb/svgl6.3k6.4k

88 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The manifest says 5.4.3, the newest tag is v5.0.0, and the package is private

Three version facts sit next to each other in package.json. The declared version is 5.4.3. The newest release tag is v5.0.0, dated 2025-09-24, with v4.1.0 from 2024-01-26 and v4.0.0 from 2023-12-17 behind it. The last push to the repository is dated 2026-10-28, so the branch is current while the tags stopped a year earlier, which is ordinary for a site whose version moves with every deploy. The more consequential field is `"private": true`. The package is scoped as @pheralb/svgl, which is the naming a publishable package would use, and the scripts list has no publish step, so nothing here is set up to be installed from a registry. What the manifest does pin is the toolchain: pnpm 11.9.0 as the declared package manager, and a list of dependencies allowed to run build scripts, esbuild and msw. The site URL field is worth a second look too, since it holds https://svgl.app?figma=1, a query parameter meant for a deep link rather than for a canonical address.

The link checker script begins with a space before the binary name

One script string carries a leading space at the start of its value:

code
 lychee --base . ./src/data/svgs.ts --cache --max-cache-age 3d . --include 'https://svgl.app'

Everything after that space is a coherent link-checking invocation. The base is the current directory, the SVG data file is named as the thing to walk, there is a cache with a three day maximum age, and an include filter that narrows the run to URLs on the project's own domain. What is questionable is the first character: a script value that opens with a space is not the command it looks like, and whether it runs at all depends on how the runner invokes it. The neighbouring checks do not have the problem. `check:size` and `check:data` are plain tsx calls into the utils directory, and `fix:viewbox` is a third script in the same style. So four utilities, three checks and one fixer, with the odd one out being the only one that reaches for an external binary.

The image runs a size check before it builds, then copies every dependency

The Dockerfile is a four-stage build on node:24-alpine with corepack enabled in both the base and the runner. The deps stage copies the manifest, the workspace file, the lockfile and .npmrc, then installs with `--frozen-lockfile` and a cache mount on the pnpm store. The builder stage copies those modules in, copies the rest of the tree, and runs two commands in order:

code
RUN pnpm run check:size
RUN pnpm run build:prod

So a size budget is a gate on the image, not a report. The runner then copies both /app/build and the builder's entire node_modules into the final stage, and only afterwards sets NODE_ENV=production, which means the modules were installed without that variable in force. It exposes port 3000 and starts `node build`. One detail is left as written: the comment above the final stage reads Production imagew. For a site whose own point is small assets, the shape of this build is the part worth measuring before you trust it.

Two generated outputs, two generators, and one field that is not an address

The production path is `pnpm build:registry && vite build`, and the first half runs tsx against utils/generate-registry.ts. Separately, `build:shadcn` runs shadcn with `--output ./static/r`, writing into a generated directory under static. So there are two build-time generators with two different tools, one feeding the site build and one writing a registry into static assets, and nothing in the file list or the scripts says which of them the deployed site serves or whether both are needed. Alongside them sits components.json at the root, the configuration that kind of CLI reads. Then there is the site URL field, which holds https://svgl.app?figma=1. A query string like that is meant to follow a click, not to define the canonical location of a site.

The API routes are a second package the production build never compiles

The tree holds an api-routes directory, a pnpm-workspace.yaml, and two scripts that treat the API as its own unit. One is `build:api`, which is `cd api-routes && pnpm build`; the other is `lint:api`, which points eslint at ./api-routes/src while `lint` covers ./src. The readme tells readers that the community extensions are all built on an API, with documentation at svgl.app/docs/api, so this directory is the part other people's software depends on. Yet the production path is `build:registry && vite build`, and the Dockerfile runs exactly that. Neither half calls build:api, so the API build is not part of the image the container recipe produces. That leaves two possibilities the repository does not settle: the API is compiled and deployed by some other route, or the documented endpoint is served by a build this Dockerfile does not run. Nothing at the root indicates which.

The readme header is a grid of links with an empty badge and a list that stops mid-word

The readme opens with HTML rather than Markdown. A centered div wraps an anchor to the site and an empty paragraph, then a second centered div holds the navigation: Explore, Sponsor this project, Getting Started, Extensions, Stack, Contributing and License, separated by decorative glyphs inside spans. Below that sits a single badge pointing at an atrox.dev actions endpoint for the repository. The stack list that follows names SvelteKit with Svelte 5, TypeScript, Content-Collections, Shiki, Tailwind CSS, bits-ui, clsx with tailwind-merge described as inspired by shadcn/ui, and Prettier with prettier-plugin-tailwindcss.

Thirteen extensions share one API and nothing else

The extensions table is the largest thing in the readme, and it holds thirteen rows with a name, a one-line description, a creator handle and a link. What they have in common is stated once, above the table: they use the SVGL API. Underneath, the differences are all in kind rather than in scope. Three are framework packages, for React, for Vue and for Svelte, the last two by the same author. Six are editor or launcher integrations, covering VSCode, Figma, Raycast, PowerToys, Flow Launcher and PowerShell, and three of those six are described in nearly the same words, search and copy SVG logos in the launcher. One is a CLI for adding icons to a project, one is a Framer plugin, one generates badges, and one is described as an AI extension for Cursor and other IDEs, listed with a link to a third-party directory rather than a repository. The links point at eight different hosts, so the table is an index of other people's work rather than a set of subpackages this repository ships.

The visible dependency list stops at svgo

The dependencies map pins exact versions rather than ranges: @shikijs/langs and @shikijs/themes at 4.4.3, shiki at 4.4.3, fuse.js at 7.5.0, jszip at 3.10.1, mode-watcher at 1.1.0, and shadcn at 4.21.0. svgo is also listed. Two things stand out. First, the syntax highlighter is pinned across all three of its packages to the same 4.4.3, so they are meant to move together. Second, shadcn sits in the runtime dependencies at 4.21.0, which is also the tool the build:shadcn script invokes; a component library's CLI appearing as a runtime dependency rather than only as a build-time one is worth knowing about before you prune anything.

Editorial conclusion

Use the site and the API rather than the package, because the manifest is marked private and nothing in it publishes anything. If you want to run the thing yourself, the Dockerfile is the shortest path and it is stricter than it looks: check:size runs before the production build, so a size budget change breaks the image rather than a warning appearing in a log. Two things to verify before you rely on it. The link checker script begins with a space before the lychee binary name, which is the kind of thing a shell will forgive and a runner will not,. And the production image copies the builder's entire node_modules, which includes development packages, before setting NODE_ENV, so expect a larger image than a production install would give you.

Frequently asked questions

How do I install the svgl package?

You do not, from this repository: the manifest sets private to true and no publish script exists, so @pheralb/svgl is not on a registry. The documented entry points are the site at svgl.app and the API documentation at svgl.app/docs/api, which the community extensions are built on.

Which version of svgl is current?

The manifest declares 5.4.3, while the newest release tag is v5.0.0 dated 2025-09-24, followed by v4.1.0 and v4.0.0. The last push to the repository is dated 2026-10-28, so the branch moves ahead of the tags.

What does the svgl link checker do, and is it wired up correctly?

It runs lychee over the SVG data file with a base of the current directory, a cache with a three day maximum age, and an include filter for https://svgl.app. The script string opens with a space before the binary name, which is the one part of it that does not read as a plain command.

Does the svgl container image build the API routes?

Not through that recipe. build:prod runs build:registry and then vite build, while the API has its own step, `cd api-routes && pnpm build`, which neither of those calls. The image also runs check:size before building, so a size budget failure stops the image build.

How many community extensions does svgl list and what kinds are they?

Thirteen rows: a CLI, npm packages for React, Vue and Svelte, a Framer plugin, a Figma plugin, integrations for VSCode, Raycast, PowerToys, Flow Launcher and PowerShell, a badge generator, and one entry described as an AI extension for Cursor and other IDEs. Each row names its creator and links to the extension.

Official sources

  1. License: MIT
  2. pheralb/svgl on GitHub
  3. Project website
  4. README
  5. Releases
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/pheralb-svgl.svg)](https://hysenlabs.com/projects/pheralb-svgl)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/pheralb-svgl.svg)](https://hysenlabs.com/projects/pheralb-svgl)

Was this useful?