Skip to content
Back to search

libraries.dev

High-crafted UI libraries for AI agents: Border beam, Orbs, Metal, Gooey, Voice, Image, Avatar bots

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/jakubantalik/libraries.dev with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/jakubantalik/libraries.dev'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/jakubantalik--libraries-dev/badge.svg)](/listings/jakubantalik--libraries-dev)

HTML

<a href="/listings/jakubantalik--libraries-dev"><img src="/api/listings/jakubantalik--libraries-dev/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 121 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Libraries.dev
  2. **High-crafted UI libraries for AI agents.** Seven React libraries for the effects that make an interface feel alive: a beam of light travelling a card's border, orbs that think while a model works, bot avatars with living faces, shapes that merge like liquid, a glow that rises with your voice, brushed metal that catches the light, and an image loader that dissolves a pixel mosaic into a real photo.
  3. Each one installs from npm and drops into your app as a single component that wraps the element you already have. Your markup keeps its semantics, the effect renders around or behind it, and the whole thing is tuned by props rather than hand-written WebGL.
  4. | Library | What it does | npm | Page |
  5. | --- | --- | --- | --- |
  6. | [Border beam](packages/border-beam) | A soft glow that rides the border of a card, button or input | `npm install border-beam` | [libraries.dev/beam](https://libraries.dev/beam) |
  7. | [Thinking orbs](packages/thinking-orbs) | Orbs that think while you wait — nine loading states for AI interfaces | `npm install thinking-orbs` | [libraries.dev/orbs](https://libraries.dev/orbs) |
  8. | [Bot avatars](packages/bot-avatars) | Animated bot avatars with living faces — eighteen glossy shapes, four states, for AI agents | `npm install bot-avatars` | [libraries.dev/avatars](https://libraries.dev/avatars) |
  9. | [Gooey](packages/liquid-gooey) | Pieces that merge like goo and morph like jelly while text stays crisp | `npm install liquid-gooey` | [libraries.dev/gooey](https://libraries.dev/gooey) |
  10. | [Voice](packages/voice-glow) | A glow that rises with your voice from the bottom of a chat input or phone screen | `npm install voice-glow` | [libraries.dev/voice](https://libraries.dev/voice) |
  11. | [Metal](packages/metal-fx) | Liquid metal for buttons, icons, text and badges, with reflections and cursor light | `npm install metal-fx` | [libraries.dev/metal](https://libraries.dev/metal) |
  12. | [Image](packages/img-fx) | A loader that becomes the image — a WebGL pixel mosaic that settles into the picture | `npm install img-fx` | [libraries.dev/image](https://libraries.dev/image) |
  13. | [Distortion waves](packages/distortion-waves) | A colourful wave that carries one screen into another — vertical, horizontal or center (SwiftUI) | `.product(name: "DistortionWavesKit", package: "Libraries.dev")` | [libraries.dev/distortion-waves](https://libraries.dev/distortion-waves) |
  14. Try each one on [libraries.dev](https://libraries.dev): a live preview to play with, the install command, the usage code, and a playground that copies the exact configuration.
  15. ## How to use
  16. Every library ships as a prompt. Copy it, paste it into your coding agent, and make it yours — three steps, no setup.
  17. 1. **Copy the prompt.** Every library page has a *Copy prompt* button. One paste gives your agent the whole library: its parameter vocabulary and your current settings.
  18. 2. **Paste it into your agent.** Drop it into Claude Code, Cursor or Codex. The agent installs the package and wires it in, matched to your theme.
  19. 3. **Make it yours.** Open the [Studio](https://libraries.dev/studio.html) with Pro for every knob, tune it live and copy the result as props.
  20. Or the plain way:
  21. ```bash
  22. npm install border-beam # or thinking-orbs, bot-avatars, liquid-gooey, voice-glow, metal-fx, img-fx
  23. ```
  24. ```tsx
  25. import { BorderBeam } from "border-beam";
  26. <BorderBeam>
  27. <button>Get started</button>
  28. </BorderBeam>
  29. ```
  30. Each package's README documents its props.
  31. ## FAQ
  32. **What do I need?** React 18 or newer. Each library is a standalone package with zero runtime dependencies, except Image, which also needs `three` as a peer dependency.
  33. **Do they work with coding agents?** Yes — that is the point. Every library installs and configures cleanly from Cursor, Claude Code and Codex, and each playground's copy-prompt button hands your agent the library's full parameter vocabulary along with your current settings.
  34. **Light and dark mode?** Both, detected for you. The default `theme="auto"` resolves a `data-theme` attribute or `dark` class on an ancestor, then falls back to `prefers-color-scheme`, updating live when either changes. Pass `theme="dark"` or `theme="light"` to pin one.
  35. **What are Pro and the Studio?** One plan across every library. Pro unlocks the [Studio](https://libraries.dev/studio.html) — deep, per-library customization beyond the public playgrounds, with export of the exact configuration — plus Pro presets and every future library and update. See [pricing](https://libraries.dev/pro.html).
  36. **Commercial projects?** The libraries are MIT — use them anywhere, including commercial work. Pro content (Studio exports, Pro presets and recipes) is licensed to you or your team under the plan you buy, for unlimited projects.
  37. **What about the models?** The code around them (MagnetKit for iOS and Android) is MIT. The model files themselves, starting with `Magnet.mfxl` for Magnetic UI, are under the [Libraries.dev Model License](LICENSE-MODEL.md): free for development, prototypes and non-commercial apps; shipping one in a commercial app needs Pro or Business. They are downloaded from libraries.dev and never committed to this repo.
  38. ## Working in this repo
  39. npm workspaces: `packages/` holds the published libraries (one folder per npm package, each with its own README and LICENSE), `sites/` the demo sites — `sites/home` is libraries.dev.
  40. ```bash
  41. npm install
  42. npm run build:site-home # every library + libraries.dev, as CI does
  43. npm run dev -w @sites/home # libraries.dev with every page and the Studio
  44. npm run typecheck # every workspace
  45. ```
  46. The home site imports the built packages, so build a library (`npm run build:beam`, `build:orbs`, `build:gooey`, `build:voice`, `build:metal`, `build:image`) before its page or bench. The standalone demos (`@sites/beam`, `@sites/gooey`, `@sites/orbs`) alias their library to its source and hot-reload without a rebuild.
  47. ## Releasing
  48. Publishing is per package (`publish.yml`, `npm publish -w <package>`): run
  49. the workflow by hand with the package name, or publish a GitHub release
  50. whose tag is `<package>@<version>` (`voice-glow@0.2.0`). A version the
  51. registry already has is skipped.
  52. ## Deploys
  53. The two sites are hosted separately, because GitHub Pages serves one custom
  54. domain per repo:
  55. - **beam.jakubantalik.com** — GitHub Pages via `.github/workflows/deploy.yml`;
  56. the domain binding lives in `sites/beam/public/CNAME`.
  57. - **gooey.jakubantalik.com** — Cloudflare Pages, built from this repo with
  58. `npm run build:site-gooey`, output `sites/gooey/dist`.
  59. - **orbs.jakubantalik.com** — Cloudflare Pages, built with
  60. `npm run build:site-orbs`, output `sites/orbs/dist`.
  61. - **libraries.dev** — Cloudflare Pages, deployed by
  62. `.github/workflows/deploy-home.yml` on every push to `main`
  63. (`npm run build:site-home`, output `sites/home/dist`). The main site:
  64. landing, a page and Studio bench per library, Pro pricing, account and
  65. legal pages. Its backend is `api.libraries.dev`, a Worker in the private
  66. `libraries-pro` repo — see `sites/home/README.md`.
  67. `.node-version` pins Node 20 for the Cloudflare builds, matching the version
  68. the GitHub workflows use; Cloudflare's default is older.
  69. Cloudflare's **Retry deployment** replays the same commit rather than fetching
  70. the branch tip, so a build that failed on an outdated commit keeps failing.
  71. Push a new commit to get a fresh one.
  72. Only the beam site carries a `public/CNAME`; that file is a GitHub Pages
  73. mechanism. The Cloudflare-hosted sites bind their domain in the Pages project
  74. instead, and the DNS record itself lives at the registrar (inetadmin), not
  75. Cloudflare — `jakubantalik.com` is not on Cloudflare's nameservers.
  76. `thinking-orbs` arrived by `git subtree`, so its full history is in this
  77. repo — but those commits touched `src/…`, not `packages/thinking-orbs/src/…`.
  78. `git log -- packages/thinking-orbs` therefore stops at the merge. To read the
  79. real history, log from the commit the merge names:
  80. ```bash
  81. git log --oneline 9c6d5c3 -- ports/ios/PillsDemo/Sources/PillsApp.swift
  82. git log --follow packages/thinking-orbs/src/index.ts
  83. ```
  84. `thinking-orbs` also carries native ports under
  85. [`packages/thinking-orbs/ports`](packages/thinking-orbs/ports) — a React
  86. Native package and a SwiftUI package, kept in step with the web renderer by
  87. the golden vectors in `spec/`. Neither is published yet.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.