Open-source project
gilbarbara/logos avatar
gilbarbara/logos

gilbarbara/logos: a hand-optimized SVG logo collection for developer and DevOps diagrams

A huge collection of SVG logos

6,857 stars755 forksSVGCC0-1.0

At a glance

What is it?
The repository ships a large set of cleaned SVG logos plus a logos.json index, and it showcases them at svglogos.dev. It is a good fit for README badges, docs diagrams and internal tooling, and a poor fit if you need a logo the maintainer has not drawn yet.
Who is it for?
Adopt gilbarbara/logos if you need clean, ready-to-embed SVG marks for developer-facing docs, diagrams or internal dashboards, and you are comfortable fetching them by name from the repository or svglogos.dev. Do not adopt it if you need a logo that is not already in the collection, because the README states that pull requests with new logos are not accepted and requests belong in the issues with links to the vector files.
Can I use it commercially?
Yes. CC0-1.0 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 4 days ago.
What is it written in?
Mainly SVG, 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.

From daily snapshots

Star history

  • gilbarbara/logos6,857 ★ · +29
Star history
Repository2026-09-232026-11-15
gilbarbara/logos6.8k6.9k

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

Editorial analysis

The problem: developer diagrams need clean vector marks, not scraped PNGs

Anyone who writes a README, an architecture diagram or a slide deck about infrastructure ends up collecting logos. The usual route is a search engine, a press kit page, or a screenshot cropped in an image editor. The results are inconsistent: some files are PNGs with white backgrounds, some are SVGs exported with a dozen empty defs and duplicated paths, some are the wrong aspect ratio. The README of gilbarbara/logos describes the collection as a curated set of SVG logos for developers, DevOps and geeks, and states that all the logos are optimized: duplicated paths removed, excessive grouping removed, empty defs removed, plus linting. That optimization step is the actual product here. The logos themselves belong to their owners, and the README says so explicitly. What the repository provides is a normalized, predictable file set with stable names, so a diagram tool can reference a logo by slug instead of by a URL that may change.

How the collection is organized: logos.json, the logos directory and a CDN

The top level of the repository contains a small number of entries: .gitattributes, .github/, CONTRIBUTING.md, LICENSE.txt, README.md, logos.json and the logos/ directory. That layout tells you most of the data flow. The logos/ directory holds the SVG files themselves, and logos.json is the index that a consumer reads to discover what exists. The site at svglogos.dev is described in the README as the place to view all of them.

Getting a logo into a README or a web page

There is no package manager install documented in the README. The README points to the repository itself and to svglogos.dev, where all logos can be viewed. If you want the collection locally, clone the repository; the logos live in the logos/ directory and the index is logos.json at the repository root.

bash
git clone https://github.com/gilbarbara/logos.git

After the clone you should see logos.json, README.md, LICENSE.txt and the logos/ directory in the working tree. If you are wiring the collection into a build step, read logos.json rather than globbing the directory, because the index is the file the project maintains alongside the SVGs. One practical check before you commit a logo to a design: open the file and confirm it has a viewBox, since an SVG without one will not scale predictably when you resize it in a diagram tool.

Requests go in the issues, not in pull requests

The contributing section is unusually direct. It states that because the maintainer optimizes all the files manually, pull requests with new logos will not be accepted, and that requests should be added in the issues, preferably with links to the vector files. This is a real constraint, not a formality. It means the collection grows at the maintainer's pace, and a logo you need today may not exist for weeks or may never be added. If your project depends on a specific brand mark that is missing, you cannot unblock yourself by opening a pull request with the file; you can only file the request and wait. The README also gives two tips for preparing SVGs, which are effectively the rules the maintainer applies: convert borders to paths, because borders use a fixed size and behave strangely when resized, and join paths into one and use it as a background or mask, or at least overlap the paths. If you submit a request, following those two rules is the fastest way to get a usable vector accepted. The same section carries the ownership caveat: all logos appearing on the site are the property of their respective owners.

Where this collection is the wrong tool

The most obvious failure mode is coverage. A curated, manually optimized set cannot be exhaustive, and the README's own list of latest logos is dominated by developer tooling and AI products: DSPy, Hermes Agent, Kimi, LlamaIndex, Meta AI, Microsoft Copilot, NotebookLM, Ollama, Pydantic, Tailscale, CrewAI. If you are building a general-purpose icon library for a consumer product, or you need logos for industries outside software, this is the wrong source. The second limitation is legal rather than technical. The repository is licensed CC0-1.0, but the README states that the logos are the property of their respective owners, so the licence on the repository does not grant you rights in the marks themselves. A CC0 dedication on the packaging does not transfer trademark permissions, and using a company's logo in a way that implies endorsement is a separate question from copying an SVG file. Third, the optimization is manual and opinionated. If you need a logo in a specific stroke weight, with a specific padding, or as a monochrome silhouette that the collection does not provide, you will be editing the file anyway, and the benefit of the collection shrinks to the initial vector. Finally, the README does not document any versioning or deprecation policy for individual logos, so a file that exists today could be renamed or removed in a later commit without a changelog entry you can track.

How it differs from icon libraries and brand asset kits

The closest alternative category is a general icon library such as Simple Icons or an icon set distributed through a package manager. The difference in approach matters. A general icon library is usually generated and versioned as a package, so you install it, pin a version, and get a programmatic API for retrieving an icon by name. That model gives you reproducibility and upgrade paths, but the icons are typically redrawn to a uniform grid and stroke style, which means they are not the official brand marks. gilbarbara/logos takes the opposite position: the files are the brand marks, cleaned up but not redesigned, and distribution is by file path rather than by a versioned package with a documented API. The trade-off is that you get fidelity to the real logo and lose the dependency management story. A second alternative is pulling each logo from the vendor's own press or brand page. That is the authoritative source and the right choice when you need the exact current mark with the vendor's own usage rules attached, but it costs you a separate lookup per logo and no consistent file naming across vendors. The third alternative is generating placeholder marks yourself, which is fine for internal diagrams and unacceptable for anything customer-facing.

Licence and maintenance cost

The repository carries CC0-1.0, which is a public domain dedication rather than a permissive software licence, and the LICENSE.txt file sits at the top level. The practical reading is that the repository's own arrangement and optimization work is offered without restriction, while the marks inside remain the property of their owners, as the README states. That split is common in logo collections and it means the licence file alone will not settle a question about displaying a third-party mark. On maintenance, the last push to the repository was on 2026-11-02, and the repository is not archived. The repository has no published GitHub releases, so there is no tagged version to pin and no changelog to read; upgrade cost is therefore the cost of re-diffing files you have vendored. If you reference logos by URL, you inherit whatever the current file is at request time, which is convenient and also means a vendor rebrand can change your rendered output without any action on your part. Vendoring the specific SVGs you use into your own repository removes that surprise at the cost of manual updates.

Editorial conclusion

Adopt gilbarbara/logos if you need clean, ready-to-embed SVG marks for developer-facing docs, diagrams or internal dashboards, and you are comfortable fetching them by name from the repository or svglogos.dev. Do not adopt it if you need a logo that is not already in the collection, because the README states that pull requests with new logos are not accepted and requests belong in the issues with links to the vector files. Before relying on it, verify the exact filename you need in logos.json, check which variants exist, and confirm that the brand you are displaying is not one whose owner objects to third-party redistribution.

Frequently asked questions

How do I install gilbarbara/logos?

There is no package manager install documented. The README links to svglogos.dev to view all logos, and the repository itself can be cloned to get the logos/ directory and the logos.json index.

Can I contribute a new logo to gilbarbara/logos with a pull request?

No. The contributing section states that because the maintainer optimizes all files manually, pull requests with new logos will not be accepted, and requests should go in the issues, preferably with links to the vector files.

What is the licence for gilbarbara/logos?

The repository is licensed CC0-1.0, with LICENSE.txt at the top level. The README separately notes that all logos appearing on the site are the property of their respective owners, so the repository licence does not by itself settle rights in the marks.

Does gilbarbara/logos have icon and dark variants?

The README does not list file names or variants; check logos.json or svglogos.dev for the variants available for a given logo.

Official sources

  1. gilbarbara/logos on GitHub
  2. Issues
  3. License: CC0-1.0
  4. Project website
  5. README
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/gilbarbara-logos.svg)](https://hysenlabs.com/projects/gilbarbara-logos)

Star history chart for your README

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

Was this useful?