thesvg
The open SVG brand library: 7,600+ brand logos and cloud icons (AWS, Azure, GCP) as official SVG. Search, copy, ship via npm, CDN, CLI, React, Vue, Svelte, Figma, VS Code, Raycast and MCP. Free, MIT, no gatekeeping.
Runssource: GitHubhomepageTypeScriptMITcommit fa87032438a2
TypeScript, MIT licensed. The project labels itself: aws, brand assets, brand logos, cdn, cloud icons, icon library, icon pack and icons.
thesvg runs. An Argusic agent installed it in 12 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
Node 22.23.4 with pnpm 12.15.0, dependencies installed, 26 vitest test files (169 tests) + 48 tsx tests all pass, Next.js 16.4.2 dev server responds HTTP 200 on / via port 3333
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 95 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node 18.19 too old for rolldown/vitest (needs node:util styleText)3 minutes
- pnpm lockfile supply-chain policy violation due to stale lockfile1 minute
- Missing @rolldown/binding-linux-x64-gnu native binding (optional dep not pulled by pnpm)1 minute
- pnpm.overrides in package.json ignored by pnpm 12 (non-fatal warning)
- Install time
- 12 minutes
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 4 hit, 3 fixed with no human help
- How the result was proved
- pnpm test exited 0 (169 vitest passed, 22 license-options + svg-path-data tests passed, 26 @thesvg/icons tests passed); curl -s -o /dev/null -w %{http_code} http://localhost:3333/ returned 200
- Model tokens used
- 49,120
- Exact commit tested
- fa87032438a2
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
# Subtest: error applies red color and cross
ok 3 - error applies red color and cross
# Subtest: throws an ApiError with network error details when fetchRegistry fetch fails
ok 1 - throws an ApiError with network error details when fetchRegistry fetch fails
# Subtest: throws an ApiError with network error details when fetchSvgContent fetch fails
ok 2 - throws an ApiError with network error details when fetchSvgContent fetch fails
# Subtest: throws an ApiError when fetchSvgContent gets a non-404 HTTP error
ok 8 - throws an ApiError when fetchSvgContent gets a non-404 HTTP error
All tests pass cleanly. Here's the result:
tokens used
49,120
All tests pass cleanly. Here's the result:Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 12 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
- Hit 4 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 12 aws projects Argusic has installed and timed, thesvg was the 8th fastest to reach a running state, and 10 of 12 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
awsbrand-assetsbrand-logoscdncloud-iconsicon-libraryicon-packiconslogosmcp-servernextjsnpm-packageopen-sourcereactsveltesvgsvg-iconssvg-logostypescriptvue
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/thesvg)Questions
- Does thesvg run?
- Yes. thesvg runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test thesvg?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fa87032438a2. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test thesvg?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does thesvg take to install?
- 12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does thesvg need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing thesvg?
- 4 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does thesvg compare with the alternatives?
- Of the 12 aws projects Argusic has installed and timed, thesvg was the 8th fastest to reach a running state, and 10 of 12 reached one at all.
- Where is the evidence for thesvg?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.