Libraries.dev
High-crafted UI libraries for AI agents: Border beam, Orbs, Metal, Gooey, Voice, Image, Avatar bots
Could not verifysource: GitHubhomepageTypeScriptMITcommit 8670e9ade047
TypeScript, MIT licensed. The project labels itself: beam, design, effect, glow, motion and product.
Argusic could not get Libraries.dev running. An Argusic agent installed it in 5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 7 npm packages (border-beam, bot-avatars, img-fx, liquid-gooey, metal-fx, thinking-orbs, voice-glow) install, build, and typecheck cleanly. The beam site serves HTML via vite dev server. The home site builds to dist/. The CLI help command works.
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 80 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.
- Container Node version (18.19.1) below repository minimum (>=20 in .node-version), causing EBADENGINE warnings
- Install time
- 5 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm run typecheck --workspaces --if-present exited 0 across 10 workspaces; curl -I on beam vite dev server returned HTTP/1.1 200 OK with Content-Type text/html; node cli/bin/libraries-dev.mjs --help printed usage and exited 0
- Model tokens used
- 40,515
- Exact commit tested
- 8670e9ade047
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Here is the final report, based solely on what I observed in this container. The repository is a monorepo of 7 React UI libraries (border-beam, bot-avatars, img-fx, liquid-gooe… **Observed results:** - `npm install` completed without errors - All 7 packages built (`npm run build:beam`, `build:orbs`, `build:gooey`, `build:metal`, `build:im… - `npm run typecheck` passed across all workspaces (border-beam, bot-avatars, img-fx, liquid-gooey,… - `npm run build:site-home` built all 7 libraries + the home site to `sites/home/dist/` - The beam site dev server served HTML with `HTTP/1.1 200 OK` on `curl -I` - `node cli/bin/libraries-dev.mjs --help` printed usage text with exit 0 - The `skills` directory, `services/studio-agent`, and `services/www-redirect` exist but are deploy… - No test suite exists in any package (no `*.test.*`, `*.spec.*`, or `__tests__` directories found) I ran `npm audit` as an information gathering step — it reported 22 vulnerabilities in transitive d…
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
- Installed in 5 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.03 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.03 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/libraries-dev)Questions
- Does Libraries.dev run?
- Argusic could not verify that Libraries.dev runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test Libraries.dev?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8670e9ade047. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Libraries.dev?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Libraries.dev take to install?
- 5 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 Libraries.dev need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Libraries.dev?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for Libraries.dev?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.